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 AioHttp, the failed_request_status_codes will control whether responses of certain status codes should be reported to Sentry. Regardless of how failed_request_status_codes is set, we will always report any unhandled exceptions where the response status is unclear to Sentry (this includes all unhandled exceptions, besides HTTPException, asyncio.CancelledError, and ConnectionResetError, which typically result in 500 errors, but are not guaranteed to).
The text was updated successfully, but these errors were encountered:
`failed_request_status_codes` allows users to specify the status codes, whose corresponding `HTTPException` types, should be reported to Sentry. By default, these include 5xx statuses, which is a change from the previous default behavior, where no `HTTPException`s would be reported to Sentry.
Closes#3535
`failed_request_status_codes` allows users to specify the status codes, whose corresponding `HTTPException` types, should be reported to Sentry. By default, these include 5xx statuses, which is a change from the previous default behavior, where no `HTTPException`s would be reported to Sentry.
Closes#3535
`failed_request_status_codes` allows users to specify the status codes, whose corresponding `HTTPException` types, should be reported to Sentry. By default, these include 5xx statuses, which is a change from the previous default behavior, where no `HTTPException`s would be reported to Sentry.
Closes#3535
For AioHttp, the
failed_request_status_codes
will control whether responses of certain status codes should be reported to Sentry. Regardless of howfailed_request_status_codes
is set, we will always report any unhandled exceptions where the response status is unclear to Sentry (this includes all unhandled exceptions, besidesHTTPException
,asyncio.CancelledError
, andConnectionResetError
, which typically result in 500 errors, but are not guaranteed to).The text was updated successfully, but these errors were encountered: