Manual Instrumentation: Tracing flow breaks with Promise interface in Ratpack 1.x async operations

[NaveenRamu]

Describe the bug

When using manual instrumentation for tracing with the OpenTelemetry API in a Ratpack 1.x application, the trace context does not propagate correctly through asynchronous operations using the Promise interface. As a result, each handler in the flow creates a new traceId, breaking the trace continuity.

This issue is observed when multiple handlers in the Ratpack pipeline use Promise for asynchronous actions. The expected behavior is that all handlers should propagate the same trace context unless explicitly set otherwise.

Steps to reproduce

Run the following project
https://github.com/NaveenRamu/ratpack1x-manualinstrumentation.git
Observe the generated traces in logs

Expected behavior

The tracing context (e.g., traceId) should propagate across asynchronous boundaries, ensuring that all operations within a single request share the same trace.

Actual behavior

Each handler creates a new traceId, resulting in disjointed traces for a single request. This disrupts the ability to trace the complete flow of the request

Javaagent or library instrumentation version

1.42.1

Environment

JDK:
OS:

Additional context

No response

[laurit]

This isn't unexpected. When doing manual instrumentation you'll have to take care of context propagation yourself. You should not expect the context to magically propagate into promise callbacks.

[github-actions]

This has been automatically marked as stale because it has been marked as needing author feedback and has not had any activity for 7 days. It will be closed automatically if there is no response from the author within 7 additional days from this comment.