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

Trace is broken in Lambda Java17 Runtime #781

Closed
wangzlei opened this issue Nov 27, 2023 · 2 comments
Closed

Trace is broken in Lambda Java17 Runtime #781

wangzlei opened this issue Nov 27, 2023 · 2 comments
Labels

Comments

@wangzlei
Copy link
Contributor

wangzlei commented Nov 27, 2023


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.

Screenshot 2023-11-20 at 2 54 11 PM

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

Copy link

github-actions bot commented Mar 3, 2024

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

Copy link

github-actions bot commented Apr 7, 2024

This issue was closed because it has been marked as stale for 30 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant