On Sep 30, 8:47 pm, Andrew Wilkinson
wrote:
> I have a patch in the bug tracker that fixes this exact problem
> -http://code.djangoproject.com/ticket/11565. The patch is just over a
> year old now so it might not apply that cleanly to the current trunk.
Revised patch here (against r13296) --
htt
I feel like something like this would be better suited to be in an
external application... since it will fail without a cache-backend.
Also, the implementation will have to change as Russell is about to
commit a logging patch with ticket #12012.
This would be best suited though for a custom handl
Hi,
Sorry the digging up an old thread, I'm a bit behind on my reading of
django-dev.
I have a patch in the bug tracker that fixes this exact problem -
http://code.djangoproject.com/ticket/11565. The patch is just over a
year old now so it might not apply that cleanly to the current trunk.
The p
Lumberjack is basically a backport of what I'd like built-in logging
support to be. I also have it built-in to django on my experimental
branch on github...
To over-ride the default email behavior just turn on the 500handler
view in lumberjack. This is what I perceive as the best method of
catch
On Thu, Sep 9, 2010 at 11:26 AM, Simon Litchfield 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 cl
This seems applicable to dcramer's django-db-log.
http://github.com/dcramer/django-db-log
This might also dovetail with logging support which may make it into
1.3, so it might be worth looping in the folks involved in that.
-justin
--
You received this message because you are subscribed to th
On 2010-09-08, at 8:29 PM, David P. Novakovic wrote:
> Hey dude,
>
> What about something like sentry or lumberjack?
Or Arecibo. There's quite a few solutions to this that don't involve sending
email. In fact I use the django taking down your email server as an example for
Arecibo all the time
Hey dude,
What about something like sentry or lumberjack?
I haven't looked at them too seriously, but I'd imagine there'd be a
way to do smarter summarizing of emails etc..?
D
On Thu, Sep 9, 2010 at 1:26 PM, Simon Litchfield wrote:
> Hi all
>
> Default behaviour of sending an email on 500 erro
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"
