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
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
The text was updated successfully, but these errors were encountered:
Sutty100
changed the title
AWS Lamba Java traces not joined
AWS Lambda Java traces not joined
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
The text was updated successfully, but these errors were encountered: