Re: rsyslog/epylog reporting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Excerpts from seth vidal's message of Mon Jun 20 10:31:02 -0400 2011:
> other ideas?

It would be interesting if we could extract Python tracebacks from our
mod_wsgi logs. For TG2, we've got WebError middleware, which can email
us tracebacks, but our TG1 apps have plenty of bugs that go unnoticed
until someone complains. Another potential solution to this problem
would be to setup an app-wide catch-all CherryPy filter[0] that we could
use in all of our TG1 apps.  This would also be a solution for "handling
FAS outages gracefully"[1].

Also, maybe a mod_security epylog module would be useful as well?

luke

[0]: http://www.turbogears.org/1.0/docs/ErrorReporting.html#method-3-application-wide-catch-all-with-cherrypy-filter
[1]: https://fedorahosted.org/fedora-infrastructure/ticket/2686
_______________________________________________
infrastructure mailing list
infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/infrastructure


[Index of Archives]     [Fedora Development]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux