Update Lambda trace IDs #361
Merged
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
added 3 commits
December 14, 2020 11:50
EkeMinusYou
pushed a commit
to EkeMinusYou/aws-xray-sdk-node
that referenced
this pull request
Jan 28, 2021
* inital commit * cleanups * updated tests
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.
Description of changes:
Ensure that Lambda trace IDs will never be
null, even outside the function handler. This extends #284. Also change the wording in the Lambda CME to clarify common cases that would cause the_X_AMZN_TRACE_IDto not be present, rather than simply stating it's not present.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.