-
Notifications
You must be signed in to change notification settings - Fork 549
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
chore: propagate context on AWS Lambda Instrumentation #424
Conversation
Without this, spans created in the lambda function are not part of the same trace as the handler span.
50952da
to
18921b9
Compare
Codecov Report
@@ Coverage Diff @@
## main #424 +/- ##
=======================================
Coverage 96.11% 96.11%
=======================================
Files 21 21
Lines 695 695
Branches 95 95
=======================================
Hits 668 668
Misses 27 27 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops, thanks!
There was a problem hiding this 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, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a typo ?
context as otelcontext, | |
context as otelContext, |
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.