sentry-python
sentry-python copied to clipboard
Check different OTel setups with POTel
Test different OTel setups with the new SDK to get a better feel of the OTel experience:
- OTel-instrumented app not instrumented by Sentry, is the Sentry span processor picking up spans and sending them to Sentry? If not, what setup is needed?
- Turning off tracing in the SDK, using OTel for tracing directly, are the errors from the SDK connected to the spans?
just to add some flavor, the table below is maybe too much but let's imagine it's the goal nice to have. Content is totally made up, in terms of check marks, i just wanted a few examples
| Framework / Library | Sentry SDK Support | OTel SDK Support | Error Support | Tracing Support | OTel Improves? | OOTB | Needs Extra Config |
|---|---|---|---|---|---|---|---|
| FastAPI | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ |
| Django | ✅ | ✅ | ✅ | ✅ | ⚠️ Adds richer spans | ✅ | 🔧 Middleware config |
| Celery | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ Instrumentation setup |
| SQLAlchemy | ✅ | ✅ | ❌ | ✅ | ✅ | ❌ | ✅ Hook into engine |
| Requests | ✅ | ✅ | ❌ | ✅ | ⚠️ Adds net.peer info | ✅ | ❌ |
Closing in favor of https://github.com/getsentry/sentry-python/issues/4658