Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[LambdaContext] persist original trace header #362

Merged
merged 1 commit into from
Oct 26, 2022

Conversation

srprash
Copy link
Contributor

@srprash srprash commented Oct 24, 2022

Issue #, if available: N/A

Description of changes:
The save_origin_trace_header method is used to persist the original trace header on the trace entity. This original trace header can later be retrieved (example) for the data field for passing through to downstreams.
We are not currently persisting the original trace header in Lambda context entity. So, when a trace header like Root=1-5759e988-bd862e3fe1be46a994272793;Parent=53995c3f42cd8ad8;Sampled=1;Foo=Bar is received by Lambda, the Foo=Bar data part is dropped when building the trace header. This PR ensures that the original trace header is persisted in the FacadeSegment on Lambda.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@srprash srprash requested a review from a team as a code owner October 24, 2022 20:13
@srprash srprash changed the title [Lambda] persist original trace header [LambdaContext] persist original trace header Oct 24, 2022
@srprash srprash merged commit 7ec8c59 into aws:master Oct 26, 2022
@srprash srprash deleted the additional_trace_data branch October 26, 2022 16:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants