-
Notifications
You must be signed in to change notification settings - Fork 476
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
Instrument Django app with Sentry and OTel and check differences. #3128
Milestone
Comments
Example traces for both scenarios: |
Scenario 1) Sentry |
Scenario 2) Sentry using Opentelementry |
Things that I noticed:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Instrument a Django application once with Sentry and once with Sentry using OpenTelementry for span creation. We want to compare the span waterfalls, to see the differences and what needs to be done to have feature parity.
Test setup:
Application: https://github.com/getsentry/demo-movie-search/tree/main/backend/django
A request to the
/api/shows/{pk}/
API endpoint will do:This resembles a common setup in production Django applications, that is used all over the planet.
Scenario 1) Sentry:
This will load Sentries integrations (like Django, Celery, ...) by default and those Sentry integrations will create spans. Opentelementry is not used.
Scenario 2) Sentry using OpenTelementry:
This will disable all Sentry span creation and spans will only be created by the OpenTelemetry SDK.
The text was updated successfully, but these errors were encountered: