Added Lineage Support to XRay Propagator using W3CBaggage #6699
Conversation
This file contains 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
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.
Leaving this PR as a draft Lambda has confirmed they are ready for this change across all OTel SDKs. Please review in the meantime.
This change is apart of an ongoing project for all of OpenTelemetry language SDKs to be moved towards support for the Lambda Lineage attribute in the X-Ray trace header via W3C Baggage. See open-telemetry/opentelemetry-java-contrib#1671 for the equivalent Java solution. This PR updates X-Ray propagator to pass lineage into baggage and inject it into outgoing X-Ray trace header.
Use of XRay Propagator will require customers to turn on both xray and baggage propagators in the environment variable (propagator,xray)