On Thursday 21 January 2010 13:59:54 James wrote: > Hi Michael, thanks for your quick reply! > Unfortunately, my deployment environment is pretty rigid but that's OK > - I can use my load balancer access logs for now and write some WSGI > middleware if needs be later on. > > That's a shame about the stack traces - I may poke around in > errormiddleware.py a little to add an optional logging target in there > too...
We have our own weberror-derived stack that allows for dumping exceptions to loggers as well as separate XML-files that can be browsed through a dedicated web-app and offer an post-mortem analysis similar to what debug-mode offers. All that's lacking is proper docs, but the code is prime-time ready (we have in production for month) Check out http://bitbucket.org/deets/ablexcser/ http://bitbucket.org/deets/ablweberror/ http://bitbucket.org/deets/ablexceptionviewer/ I'm planning to release that stuff soon. The separation into errorreporter (currently called excser, gonna change that) is because we wanted to have a exception reporting mechanism that works for all our python-code ,not only web-based. Diez
-- You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en.
