fix(otel): fix span and trace ids for distributed tracing #801
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.
trace id
== Sentrytrace id
in the scenario where we continue a remote trace, therefore we need to go back to the staticSPAN_MAP
to rely on the Sentrytrace_id
.span id
== Sentryspan id
when continuing a remote trace, so I've updated that API.Noticed this during manual testing.
I should update the integration tests to cover more scenarios.