feat(node-experimental): Sync OTEL context with Sentry AsyncContext #8797
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.
This PR implements a strategy to sync the OpenTelemetry Context with our own Hub forking for AsyncContext.
This works by fully relying on OpenTelemetry to handle async context isolation/forking.
This means we do not need to do any context forking ourselves anymore, so no need for e.g.
Sentry.Handlers.requestHandler()
and stuff like this.It should also mean that Sentry & OTEL should be as in sync as possible.
Some notes: