Nic

@dabarrell , have you had any update on this?

+1 Fairly certain we're seeing the same issue in a similar setup we have, trying to auto-instrument Java Lambdas using otel java agent layer. I'd reached out to the community...

Thanks for your work on this @wpessers > OpenTelemetry trace context is injected as SQS MessageAttributes, so the service receiving the message can link cascading spans to the trace which...

> I haven't looked deeply into the instrumentation code, but am currently thinking that maybe the propagation of the context doesn't work because we are using event source mapping. Meaning...

Thanks for [the clear explanation](https://github.com/open-telemetry/opentelemetry-lambda/issues/1787#issuecomment-2896956917) @serkan-ozal 👍 . Totally understand how traceId propagation in batched SQS message handling is not straightforward. I've seen that some of our SQS handler Lambdas...

In the meantime...we're using [the Java Agent Lambda layer](https://github.com/open-telemetry/opentelemetry-lambda/blob/main/java/README.md) to instrument our Lambda. To support our deployments where we know batch size is 1, if we wanted to roll our...

> But have you tried using the wrapper layer... > If yes, what did that result in? I've tested this, and the below dropdown contains a reminder of how this...

> It is in fact trivial to use the trace context that is put into the message attributes to parse the context at your receiving end and then link back...