Skip to content

docs(python): Document failed_request_status_codes option for Django #19118

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ericapisani merged 1 commit into from
Aug 28, 2026
Merged

docs(python): Document failed_request_status_codes option for Django #19118

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions docs/platforms/python/integrations/django/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -249,6 +249,24 @@ Note that `OPTIONS` and `HEAD` are excluded by default.

</SdkOption>

<SdkOption name='failed_request_status_codes' type='set[int]' defaultValue='{*range(500, 600)}'>

A set of integers that will determine which status codes should be reported to Sentry.

The `failed_request_status_codes` option determines whether exceptions handled within Django should be
reported to Sentry. Unhandled exceptions that don't have a `status_code` attribute will always be reported to Sentry.

Examples of valid `failed_request_status_codes`:
- `{500}` will only send events on HTTP 500.
- `{400, *range(500, 600)}` will send events on HTTP 400 as well as the 5xx range.
- `{500, 503}` will send events on HTTP 500 and 503.
- `set()` (the empty set) will not send events for any HTTP status code.

The default is `{*range(500, 600)}`, meaning that all 5xx status codes are reported to Sentry.

</SdkOption>


## Next Steps

<PlatformContent includePath="getting-started-next-steps" />
Expand Down
Loading