+1 for django-sentry. I use it on even the smallest sites and it works great there too.
Brian On Sun, Jun 19, 2011 at 9:17 AM, graeme <[email protected]> wrote: > What is the simplest way of preventing the flood of emails that > results from a site wide error? I do not want to end up with 10,000 > emails because the database was down for an extended period. > > I do not want to turn it off with ADMINS = () because it is useful for > reporting one-off errors. > > I cannot limit at the mail server because the site is on shared > hosting. > > Django Sentry seems to be able to email an error only the first time > it is seen, but it seems overkill for a very simple site - its bigger > than the apps that run the site combined and it introduces an external > dependency on a site that has only has one (other than Django and the > database driver that is!), and even that is non-critical. > > Are there any other options? > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- Brian Bouterse ITng Services -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
