sentry-python
sentry-python copied to clipboard
getsentry
The official Python SDK for Sentry.io
### How do you use Sentry? Sentry Saas (sentry.io) ### Version 2.40.0 ### Steps to Reproduce Start a transaction and call `add_feature_flag`, then finish the transaction and have it sent...
Remove experimental options that are not relevant anymore or that are superseded by non-experimental options (e.g. logs, profiler options). POTel PR for logs: [https://github.com/getsentry/sentry-python/pull/4653](https://github.com/getsentry/sentry-python/pull/4653)
Likely needs [https://github.com/getsentry/sentry-python/issues/4999](https://github.com/getsentry/sentry-python/issues/4999)
Go over the docs and double-check all major changes are documented.
We can likely reuse big parts of the original migration guide for POTel. See getsentry/sentry-docs#15240 for the PR that removed it.
`StrawberryIntegration` shouldn't be auto-enabling since it cannot reliably auto-detect whether it should enable the sync or async version of the instrumentation. Users should make the choice explicitly.Additional context in [https://github.com/getsentry/sentry-python/issues/4980](https://github.com/getsentry/sentry-python/issues/4980)
It's confusing. We can change this to only log `logger.exception()`s (requires https://github.com/getsentry/sentry-python/issues/4983), or not create events by default at all.
Placeholder to not forget to sync regarding any breaking changes required for span streaming.
eventlet was discontinued years ago. POTel PR: https://github.com/getsentry/sentry-python/pull/4584
Once [https://github.com/getsentry/sentry-python/issues/4999](https://github.com/getsentry/sentry-python/issues/4999) is done, go through our integrations and see which legacy versions we can drop. POTel PR: https://github.com/getsentry/sentry-python/pull/4246 (get inspired but see if there's anything else that makes sense...