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
We are faced with a strange number of the 500 errors in our metrics (which are collected by aiodogstatsd.contrib.aiohttp middleware) and that number was different from what we at ALB logs. The reason for this - is that when the connection is aborted before we processed it, the CancelledError would be raised -- and it will be counted as a 500 error, but this is not true -- user will not receive any response in that case.
Expected behavior
In the case of CancelledError it would be great to have the option to separate it from other errors and have an option to skip it from the metrics
try:
response=awaithandler(request)
response_status=response.statusexceptweb.HTTPExceptionase:
response_status=e.statusraiseeexceptCancelledError:
response_status= ... # some code, that will indicate that is `CancelledError`finally:
if_proceed_collecting(..., collect_canceled=True/False): # allow to mute CancelledError metric
...
The text was updated successfully, but these errors were encountered:
Hi,
Description
We are faced with a strange number of the
500 errors
in our metrics (which are collected byaiodogstatsd.contrib.aiohttp
middleware) and that number was different from what we at ALB logs. The reason for this - is that when the connection is aborted before we processed it, theCancelledError
would be raised -- and it will be counted as a 500 error, but this is not true -- user will not receive any response in that case.Expected behavior
In the case of
CancelledError
it would be great to have the option to separate it from other errors and have an option to skip it from the metricsThe text was updated successfully, but these errors were encountered: