Skip to content

Check different OTel setups with POTel #4236

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.

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

Open
sentrivana opened this issue Apr 3, 2025 · 1 comment
Open

Check different OTel setups with POTel #4236

sentrivana opened this issue Apr 3, 2025 · 1 comment

Comments

@sentrivana
Copy link
Contributor

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?
@smeubank
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants