Lettuce traces are not attached to a parent context when using telemetry module without Java Agent

[Kresshy]

Describe the bug

We have a manually configured SDK in our services and we added the Lettuce Telemetry module to our codebase to produce traces for Redis queries. The documentation shows it is supported.

We can see the produced spans but it is not attached to an existing parent context. These spans have their own traces with a new trace id, and this is the only span under that trace.

I assume the OTEL context is not propagated to the executor which is used by the lettuce library.

I would like to avoid providing an executor externally where I have to use Context#taskWrapping(Executor) to make this happen and rather rely on the default internal executor of the lettuce library.

Steps to reproduce

• We are using Java 11 & Lettuce 6.4.0
• Manually configure OTEL SDK.
• We use gRPC telemetry as well so our parent spans are usually gRPC traces.
• Manually initialize LettuceTelemetry and provide it for lettuceClientResources:

lettuceTelemetry = LettuceTelemetry.create(GlobalOpenTelemetry.get());

...
...

clientResourcesBuilder.tracing(lettuceTelemetry.newTracing()).build();

• When executing Redis queries the produces spans should be attached to the correct parent spans.

Expected behavior

• The produced spans should be under the correct parent spans/context.

Actual behavior

• The produced spans are independent, the are not attached to any parents.

Javaagent or library instrumentation version

No java agent, openTelemetryVersion = "1.47.0", openTelemetryInstrumentationVersion = "2.13.1(-alpha)", openTelemetryContribVersion = "1.44.0-alpha"

Environment

JDK: Temurin JDK 11

Additional context

No response

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[breedx-splk]

Since you're doing manual tracing without the agent, it simply sounds like there is no context at the time the lettuce client is creating its spans. Are you sure there's an existing context? If so, how is that being created? Without the agent, a gRPC parent span wouldn't be created automatically for you....

[laurit]

Could you provide a minimal application that reproduces the issue.

[Kresshy]

I'm using the experimental tracing feature of gRPC Java: https://github.com/grpc/grpc-java/blob/a40d549ced82becbb12ca6f6b0e007cd430555a6/opentelemetry/src/main/java/io/grpc/opentelemetry/GrpcOpenTelemetry.java#L70

• Without the Java Agent context propagation is manual in some cases, as I saw Lettuce client uses an internal executor and the context does not propagate to that.
• I can provide an external executor wrapped with Context#taskWrapping() but I'm not comfortable doing that and rather would prefer if lettuce could support the OTEL context propagation even when there is no agent present.

The reason I'm asking for this is because I saw lettuce telemetry supports standalone library instrumentation. So in this case, who should be responsible to propagate the context?

https://opentelemetry.io/docs/zero-code/java/agent/supported-libraries/

[Kresshy]

I'm also happy to provide a minimal application, let me know what format and where should I share it?

[laurit]

I'm also happy to provide a minimal application, let me know what format and where should I share it?

a github repo that can be cloned would be the best