Java Agent Lambda Layer Not Sending all Traces about aws-otel-lambda HOT 7 CLOSED

Hi @otj202 - that isn't expected behavior indeed if you haven't reconfigured the sampler. Can you try enabling debug logging -Dotel.javaagent.debug=true to see if there are any errors logged?

https://github.com/open-telemetry/opentelemetry-java-instrumentation#troubleshooting

from aws-otel-lambda.

Hey, I dont think I can pass a system property because i'm running on lambda. can i set an environment variable to do this?

from aws-otel-lambda.

@otj202 Ah yeah, then you can do OTEL_JAVAAGENT_DEBUG=true

from aws-otel-lambda.

Im getting this error:

java.lang.ClassNotFoundException: io.grpc.netty.NettyChannelProvider

and then later

[opentelemetry.auto.trace 2021-08-31 00:59:57:945 +0000] [main] DEBUG io.opentelemetry.extension.trace.propagation.B3PropagatorExtractorMultipleHeaders - Invalid TraceId in B3 header: null'. Returning INVALID span context.

, but the second one only appears sometimes!

I made 10 requests and none of them tracked the call to DynamoDB in XRay. They only tracked invocation/overhead, and showed the above error in logs.

Then after that went cold(got deallocated on lambda), I made 20 requests and all of them tracked the call to DynamoDB in XRay, and didnt show the error.

Maybe Its an error that occurs on the initialization of the lambda function?

from aws-otel-lambda.

any progress on this? I've just been using the XRAY sdk in the mean time, but would prefer to use this .

from aws-otel-lambda.

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

from aws-otel-lambda.

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

from aws-otel-lambda.