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
We are using AWS Java Lambda along with otel lambda ARN arn:aws:lambda:us-east-1:184161586896:layer:opentelemetry-javaagent-0_1_0:1 to auto instrument the application flow. Whenever lambda is triggered we are seeing same traceid and corresponding spans being sent multiple times to collector, in our case atleast 3 times which is an issue for us.
For example:
Jul 19 17:21:10 ip-xx.ec2.internal otelcol[567034]: Trace ID : 2c2448453e8bb55f9aff1fc984d19c2b
Jul 19 17:21:11 ip-xx.ec2.internal otelcol[567034]: Trace ID : 2c2448453e8bb55f9aff1fc984d19c2b
Jul 19 17:21:11 ip-xx.ec2.internal otelcol[567034]: Trace ID : 2c2448453e8bb55f9aff1fc984d19c2b
Steps to reproduce
Its a Spring Boot application having outbound calls to couple of other aws services like secrets, dynamodb
What did you expect to see?
We were expecting to see 1 traceId and its corresponding spans only once
What did you see instead?
We are seeing 3 calls being triggered every time lambda is triggered
What version of collector/language SDK version did you use?
(arn:aws:lambda:us-east-1:184161586896:layer:opentelemetry-javaagent-0_1_0:1)
What language layer did you use?
Java - Spring boot App
Additional context
We saw x-ray was enabled in AWS Lambda, we did try to disable and run the same app but still the issue persists
The text was updated successfully, but these errors were encountered:
Hi @sanjyoth@ajaynagariya I am happy to help on this issue.
How do you deploy your Spring boot app into AWS Lambda?
Is it possible to share a sample project to reproduce this issue?
Describe the bug
We are using AWS Java Lambda along with otel lambda ARN arn:aws:lambda:us-east-1:184161586896:layer:opentelemetry-javaagent-0_1_0:1 to auto instrument the application flow. Whenever lambda is triggered we are seeing same traceid and corresponding spans being sent multiple times to collector, in our case atleast 3 times which is an issue for us.
For example:
Jul 19 17:21:10 ip-xx.ec2.internal otelcol[567034]: Trace ID : 2c2448453e8bb55f9aff1fc984d19c2b
Jul 19 17:21:11 ip-xx.ec2.internal otelcol[567034]: Trace ID : 2c2448453e8bb55f9aff1fc984d19c2b
Jul 19 17:21:11 ip-xx.ec2.internal otelcol[567034]: Trace ID : 2c2448453e8bb55f9aff1fc984d19c2b
Steps to reproduce
Its a Spring Boot application having outbound calls to couple of other aws services like secrets, dynamodb
What did you expect to see?
We were expecting to see 1 traceId and its corresponding spans only once
What did you see instead?
We are seeing 3 calls being triggered every time lambda is triggered
What version of collector/language SDK version did you use?
(arn:aws:lambda:us-east-1:184161586896:layer:opentelemetry-javaagent-0_1_0:1)
What language layer did you use?
Java - Spring boot App
Additional context
We saw x-ray was enabled in AWS Lambda, we did try to disable and run the same app but still the issue persists
The text was updated successfully, but these errors were encountered: