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

AWS Lambda Java traces not joined #1033

Open
Sutty100 opened this issue Jan 3, 2025 · 1 comment
Open

AWS Lambda Java traces not joined #1033

Sutty100 opened this issue Jan 3, 2025 · 1 comment

Comments

@Sutty100
Copy link

Sutty100 commented Jan 3, 2025

Describe the bug
When Lambda A calls Lambda B via API Gateway the trace is not joined up in either Elastic APM, Zipkin however it is in X-RAY.

Steps to reproduce
Create two Lambdas that are both invoked via API Gateway. Have the first lambda call the second via API Gateway. Have an OpenTelemetry collector exporting to X-RAY, Elastic, Zipkin.

What did you expect to see?
A single trace showing Lambda A calling Lambda B in Zipkin and Elastic not just XRAY.

What did you see instead?
Two separate traces with Lambda A showing an outgoing http request

What version of collector/language SDK version did you use?
Lambda Layer: aws-otel-java-agent-amd64-ver-1-32-0:3
Java Version: 21
OpenTelemetry Collector: opentelemetry-collector-contrib:0.116.1

@Sutty100 Sutty100 changed the title AWS Lamba Java traces not joined AWS Lambda Java traces not joined Jan 3, 2025
@Sutty100
Copy link
Author

Sutty100 commented Jan 3, 2025

Realised I've already opened an issue which has closed as stale!

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

No branches or pull requests

1 participant