[Fix] Update AWS SDK Instrumentation to inject XRay trace context into HTTP Headers #131
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:
Fixes the absence of broken X-Ray context propagation when the underlying HTTP instrumentation is suppressed or disabled.
Similarly to Java and Python, AWS SDK Js instrumentation itself should be able to inject the X-Ray Context into the HTTP Headers:
Note - If the underlying HTTP instrumentation is enabled, then the underlying HTTP Child Span of the AWS SDK Span will overwrite the Trace Context to propagate through headers.
Description of changes:
patches/extended-instrumentations/directoryAwsSdkInstrumentationExtendedclass that extends upstream AwsInstrumentation to override its patching mechanism of thesendmethod. The overridden method will additionally update the AWS SDK middleware stack to inject theX-Amzn-Trace-IdHTTP header.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.