Not Heroku, but in general...
On Friday, January 10, 2020 at 9:21:36 PM UTC-5, Peter Lada wrote: > > > If anyone has a good insight on how to enable further request logging > (beyond the path that heroku already gives me) that would be great. > You could write a simple tween, modeled after pyramid_exclog ( https://github.com/Pylons/pyramid_exclog) that times the request (and possibly checks the CPU load); then logs pertinent information about the request to a database if thresholds are met. I've used this approach to grab GET/POST vars and Paths to identify and recreate edge cases. You could also do this with Sentry; their API allow custom events, beyond standard exception logging. I'd also look at your HTTP and Google Analytics logs to for any patterns when these issues spike. I don't know if this is possible on Heroku, but I still use Statsd timing to log certain types of sever activity (like db connection management actions) - and look for any changes in behavior after a release. But... Based on what you've disclosed: 1) nothing makes this look particularly waitress related, and not something like traffic spikes, or spikes or problematic routes. I know nothing about your apps, but most sites I've worked on have the lowest traffic of the year between Dec 23-Jan 7. 2) if this were waitress related, i'd be suspect of the entire 1.4 release family and not just the ones you identified. there were a handful of changes in in 1.4.0 ( https://docs.pylonsproject.org/projects/waitress/en/stable/#id4) -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/23bde29f-7661-4b23-ab7a-66e8a68565c3%40googlegroups.com.
