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

chore: propagate context on AWS Lambda Instrumentation #424

Merged
merged 2 commits into from
Apr 22, 2021

Conversation

gregoryfranklin
Copy link
Contributor

Which problem is this PR solving?

Context is not propagated. This means the span created by the AWS Lambda Instrumentation is not part of the same trace as spans created within the lambda function.

Short description of the changes

Add the span created by the AWS Lambda Instrumentation to the context that the lamdba function is run with.

@gregoryfranklin gregoryfranklin requested a review from a team April 15, 2021 12:51
Without this, spans created in the lambda function are not part of the
same trace as the handler span.
@codecov
Copy link

codecov bot commented Apr 15, 2021

Codecov Report

Merging #424 (2a116f2) into main (86708bc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #424   +/-   ##
=======================================
  Coverage   96.11%   96.11%           
=======================================
  Files          21       21           
  Lines         695      695           
  Branches       95       95           
=======================================
  Hits          668      668           
  Misses         27       27           

Copy link
Contributor

@anuraaga anuraaga left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops, thanks!

Copy link
Member

@obecny obecny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@@ -24,7 +24,9 @@ import {
safeExecuteInTheMiddle,
} from '@opentelemetry/instrumentation';
import {
context as otelcontext,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a typo ?

Suggested change
context as otelcontext,
context as otelContext,

@vmarchaud vmarchaud merged commit 21d1701 into open-telemetry:main Apr 22, 2021
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.

5 participants