[SVLS-4298] Java upstream sqs trace context propagation #454
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.
What does this PR do?
This is python's version of the same logic done in the NodeJS layer PR DataDog/datadog-lambda-js#511
Motivation
JAVA lambda would put trace context information in the
AWSTracerHeader
inside themessage.attributes
This PR extract that so that JAVA Lambda => sqs => python lambda would show as one connected trace.
Additional Notes
I refrained from refactoring too much of the code logic in this PR. But I plan to do some refactoring in a following PR. This is because the refactoring would focus more on the general structure of the extractors. Therefore not very relevant to the java upstream case here.
Testing Guidelines
Added unittest case using a java upstream example payload.
Manually tested in a real lambda setup:
Types of Changes
Check all that apply