[LambdaContext] persist original trace header #362
Merged
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.
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 thedata
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, theFoo=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.