Dual POTel setup improvements #4401
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
TracerProvider
already exists, patch it.TracerProvider
is a singleton, so if we aren't the first one setting it up, we need to use the existing one.TracerProvider
after each test so that we start with a clean slate and it gets set up anew oninit
.instrumentation_scope.name
(e.g.opentelemetry.instrumentation.flask
) and turn it intoorigin
at the end. This allows us to differentiate between spans auto-instrumented by Sentry and OTel.