getsentry/sentry-python (sentry-sdk)
### [`v2.5.0`](https://togithub.com/getsentry/sentry-python/blob/HEAD/CHANGELOG.md#250)
[Compare Source](https://togithub.com/getsentry/sentry-python/compare/2.4.0...2.5.0)
##### Various fixes & improvements
- Allow to configure status codes to report to Sentry in Starlette and FastAPI ([#3008](https://togithub.com/getsentry/sentry-python/issues/3008)) by [@sentrivana](https://togithub.com/sentrivana)
By passing a new option to the FastAPI and Starlette integrations, you're now able to configure what
status codes should be sent as events to Sentry. Here's how it works:
```python
from sentry_sdk.integrations.starlette import StarletteIntegration
from sentry_sdk.integrations.fastapi import FastApiIntegration
sentry_sdk.init(
```
### ...
integrations=[
StarletteIntegration(
failed_request_status_codes=[403, range(500, 599)],
),
FastApiIntegration(
failed_request_status_codes=[403, range(500, 599)],
),
]
)
```
`failed_request_status_codes` expects a list of integers or containers (objects that allow membership checks via `in`)
of integers. Examples of valid `failed_request_status_codes`:
- `[500]` will only send events on HTTP 500.
- `[400, range(500, 599)]` will send events on HTTP 400 as well as the 500-599 range.
- `[500, 503]` will send events on HTTP 500 and 503.
The default is `[range(500, 599)]`.
See the [FastAPI](https://docs.sentry.io/platforms/python/integrations/fastapi/) and [Starlette](https://docs.sentry.io/platforms/python/integrations/starlette/) integration docs for more details.
- Support multiple keys with `cache_prefixes` (#3136) by @sentrivana
- Support integer Redis keys (#3132) by @sentrivana
- Update SDK version in CONTRIBUTING.md (#3129) by @sentrivana
- Bump actions/checkout from 4.1.4 to 4.1.5 (#3067) by @dependabot
```
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
2.4.0->2.5.0Release Notes
getsentry/sentry-python (sentry-sdk)
### [`v2.5.0`](https://togithub.com/getsentry/sentry-python/blob/HEAD/CHANGELOG.md#250) [Compare Source](https://togithub.com/getsentry/sentry-python/compare/2.4.0...2.5.0) ##### Various fixes & improvements - Allow to configure status codes to report to Sentry in Starlette and FastAPI ([#3008](https://togithub.com/getsentry/sentry-python/issues/3008)) by [@sentrivana](https://togithub.com/sentrivana) By passing a new option to the FastAPI and Starlette integrations, you're now able to configure what status codes should be sent as events to Sentry. Here's how it works: ```python from sentry_sdk.integrations.starlette import StarletteIntegration from sentry_sdk.integrations.fastapi import FastApiIntegration sentry_sdk.init( ``` ### ... integrations=[ StarletteIntegration( failed_request_status_codes=[403, range(500, 599)], ), FastApiIntegration( failed_request_status_codes=[403, range(500, 599)], ), ] ) ``` `failed_request_status_codes` expects a list of integers or containers (objects that allow membership checks via `in`) of integers. Examples of valid `failed_request_status_codes`: - `[500]` will only send events on HTTP 500. - `[400, range(500, 599)]` will send events on HTTP 400 as well as the 500-599 range. - `[500, 503]` will send events on HTTP 500 and 503. The default is `[range(500, 599)]`. See the [FastAPI](https://docs.sentry.io/platforms/python/integrations/fastapi/) and [Starlette](https://docs.sentry.io/platforms/python/integrations/starlette/) integration docs for more details. - Support multiple keys with `cache_prefixes` (#3136) by @sentrivana - Support integer Redis keys (#3132) by @sentrivana - Update SDK version in CONTRIBUTING.md (#3129) by @sentrivana - Bump actions/checkout from 4.1.4 to 4.1.5 (#3067) by @dependabot ```Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.