Re: Ability to save 4xx messages to database

2013-04-11 Thread Anton Strogonoff
(A side-note, you actually can use Sentry for 404s as well with contrib middleware. It does the job, although for one project we re-implemented it to log 404s as DEBUG messages instead of INFO, just copied the class and changed a

Re: Ability to save 4xx messages to database

2013-04-11 Thread Javier Guerra Giraldez
On Thu, Apr 11, 2013 at 2:09 PM, Babatunde Akinyanmi wrote: > Hi Javier, why no for small deployments, with a single django app server, just logging to a file and analyzing with grep works really really well. for larger deployments, where you have more than one django instance, it makes sense to

Re: Ability to save 4xx messages to database

2013-04-11 Thread Michael Manfre
ne > From: Javier Guerra Giraldez > Sent: 4/11/2013 4:30 PM > To: django-developers@googlegroups.com > Subject: Re: Ability to save 4xx messages to database > On Thu, Apr 11, 2013 at 10:21 AM, Val Neekman wrote: > > Now, the $64 K question: is Django a good place for this? > &

RE: Ability to save 4xx messages to database

2013-04-11 Thread Babatunde Akinyanmi
Hi Javier, why no Sent from my Windows Phone From: Javier Guerra Giraldez Sent: 4/11/2013 4:30 PM To: django-developers@googlegroups.com Subject: Re: Ability to save 4xx messages to database On Thu, Apr 11, 2013 at 10:21 AM, Val Neekman wrote: > Now, the $64 K question: is Django a good pl

Re: Ability to save 4xx messages to database

2013-04-11 Thread Javier Guerra Giraldez
On Thu, Apr 11, 2013 at 10:21 AM, Val Neekman wrote: > Now, the $64 K question: is Django a good place for this? I'd say no. the best place would be a monitoring system. a surprisingly good approach is to use rsyslog protocol, and add a good event storage backend to the centralizing rsyslogd. i