On Thu, Sep 9, 2010 at 11:26 AM, Simon Litchfield <si...@slicmedia.com> wrote: > Hi all > > Default behaviour of sending an email on 500 error is great. > > Problem is on high traffic sites, and you might just be making a quick > update- literally within seconds you can bring your mail server down- > crash your mail client- or render your gmail account useless. > > With "batteries included" and "production ready" ethos in mind, I > reckon this needs fixing. > > 1) Max emails per minute setting > > 2) Include alternative error handler middleware in core > > I haven't tried it yet, but this looks interesting (note web2py > includes this) -- > http://bitbucket.org/ashcrow/django-error-capture-middleware/wiki/Home > > Thoughts? I know I'm not the only one who has run into this (Russ?)
This exact problem is the reason why adding logging support is on my todo list for 1.3. Essentially, the idea is that by merging Vinay's logging work, the current behavior of 'send an email on server error' can become a configuration item; the default configuration would be to send an email (for backwards compatibility), but this setting could be easily modified to be 'write to a file', 'write to syslog', 'post to Arecibo', 'write to database', or any other logging handler you care to write and install -- potentially multiple handlers, if required. If you want to keep email error handling but want to avoid the problems you describe, you can then write (and install) a custom error logging handler that has the properties you describe. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
