Take trace id always from propagation context#2209
Merged
antonpirker merged 22 commits intomasterfrom Jul 4, 2023
Merged
Conversation
…to be the behavior in 1.25.0
…id-always-from-propagation-context2
sl0thentr0py
requested changes
Jun 29, 2023
4a29b6f to
12e5301
Compare
sl0thentr0py
approved these changes
Jun 30, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Make sure that the trace information is always taken from propagation context. (was not the case if you create a span without a transaction, which is happening if you have a vanilla Python without any Integrations and you make an outgoing HTTP request)