You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
name: Bug report
about: Create a report to help us improve
title: ''
labels: bug
assignees: ''
Describe the bug
Using the latest ADOT Java lambda layerarn:aws:lambda:us-west-2:901920570463:layer:aws-otel-java-agent-amd64-ver-1-31-0:1 in Lambda java 17 runtime causes broken trace. The same layer works fine in Lambda java 11 Runtime.
This issue is stale because it has been open 90 days with no activity. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled
name: Bug report
about: Create a report to help us improve
title: ''
labels: bug
assignees: ''
Describe the bug
Using the latest ADOT Java lambda layer
arn:aws:lambda:us-west-2:901920570463:layer:aws-otel-java-agent-amd64-ver-1-31-0:1
in Lambda java 17 runtime causes broken trace. The same layer works fine in Lambda java 11 Runtime.Solution
A minimal patch of upstream PR open-telemetry/opentelemetry-java-instrumentation#8368
Steps to reproduce
Load ADOT java layer in a Lambda function in java17 Runtime
What did you expect to see?
End to end trace from AWS Lambda service segment to user's Lambda function handler segments
What did you see instead?
ADOT layer creates a new trace id, user gets broken trace
What version of collector/language SDK version did you use?
Version: (e.g.,
v0.58.0
,v1.11.0
, etc)What language layer did you use?
Java
Additional context
Refer to OpenTelemetry issue open-telemetry/opentelemetry-java-instrumentation#7579
The text was updated successfully, but these errors were encountered: