You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example when url is too long, gunicorn will respond with 400 and a short html, but access or error logs are not written.
This makes it harder to diagnose an issue when all you have is server side metrics/logs.
There are debug logs but debug level is too noisy to enable in production.
Does it make sense to add access/error/exception logging to handle_error for this class of issues?
The text was updated successfully, but these errors were encountered:
For example when url is too long, gunicorn will respond with 400 and a short html, but access or error logs are not written.
This makes it harder to diagnose an issue when all you have is server side metrics/logs.
There are debug logs but debug level is too noisy to enable in production.
Does it make sense to add access/error/exception logging to
handle_error
for this class of issues?The text was updated successfully, but these errors were encountered: