William Armiros

Hi @stijndehaes, thanks for following up. We will be cutting a release as soon as able to get this fix out.

Hi @dasuma - we do not have instrumentation for either of those frameworks in the X-Ray SDK, nor do we have plans to add them. They are supported by OpenTelemetry...

Hi @pm98zz-c, Thanks for this write up, I think it is a valid proposal and we area always open to pull requests! Also, The AWS Distro for OpenTelemetry for tracing...

CI failing because of deprecated commands, will rerun after fix.

Discussing with AWS SDK team whether this PR reflects desired behavior - will need to wait on merging.

@Psykar that workaround should work, as long as you have X-Ray permissions on your lambda. Just also make sure to attach the correct trace ID, parent ID, and sample decision...

@mariotoffia unfortunately the blocking issue for connecting SQS -> Lambda is a fundamental AWS problem not specific to a language, so it is ultimately the same tracking issue as https://github.com/aws/aws-xray-sdk-node/issues/208....

Short term mitigation: Update https://aws-otel.github.io/docs/getting-started/lambda/lambda-java doc page to indicate only the 1 kind of APIGW event object is supported Long term mitigation: actually fix the Lambda Java instrumentation code to...

Hi @dsharkou, have you tried following the AWS Lambda layer instructions with the .NET 6 runtime? The upstream OTel library should support .NET 6, and the layer will not be...

> After a bunch of refactoring to get AWSXRayIdGenerator and AWSXRayPropagator working @ianwremmel why did you need to refactor to get these components to work? They should work out of...