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

Question - ADOT Lambda Layer Nodejs - SQS AWSTraceHeader is not propogated to Lambda #2074

Open
vdepatla opened this issue Apr 2, 2024 · 0 comments

Comments

@vdepatla
Copy link

vdepatla commented Apr 2, 2024

Hello Team,

I am using ADOT nodejs layer for my lambda function(This internally uses opentelemetry-js-contrib) which receives messages from SQS. attributes section in SQS event looks like below.

"attributes":{"ApproximateReceiveCount":"1","AWSTraceHeader":"Root=1-6be18c9f-da14c537235206057392a4c5;Parent=3f2b6d1e7fb5dfa5;Sampled=1","SentTimestamp":"1712067141206","SenderId":"AROA3BFWJP323VSCRBO2Z:66a19705db6549f698be35b063883238","ApproximateFirstReceiveTimestamp":"1712067141208"}

However in my lambda shows a different TraceID

@opentelemetry/instrumentation-net 0.32.4\nSpan #0\n Trace ID : 660c1247f12e5bdc1663c58843d53f49\n Parent ID : 793df25914b9005c\n ID : 6c80e6026b5d6226

Do I need additional settings/code on the lambda handler for AWSTraceHeader to be propogated to my lambda function ?

I see there is eventContextExtractor here https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/node/opentelemetry-instrumentation-aws-lambda how can I pass this from lambda layer ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant