It's using the python stdlib logging library. You can add a handler to that
logger that sends emails or does anything else. It really depends on how you're
running your processes how to setup logging properly but in Pyramid (which uses
logging.config.fileConfig) it would be done by adding
I understand the cause of the warning, I just wonder if there's a way to
hook into the process that triggers it to allow it to send a warning email
or something when the queue depth reaches a certain threshold?
Alternatively is there a way to query it to see what the queue depth is
currently?
One of my CI tests deals with an edge case, in which a HTTPMovedPermanently
is raised in deeply nested code. This almost never gets raised in
Production - rules on the loadbalancer/gateway typically catch it.
With the debugtoolbar off, Pyramid serves the redirect. With the
debugtoolbar
Hello up there,
A new release of the package to convert URI into ZODB storage just came out.
The highlight of this release is added support for `demo:` URI resolver. For
example
demo:(zeo://localhost:9001?storage=abc)/(file:///path/to/Changes.fs)
refers to DemoStorage that combines ZEO
