OpenTelemetry TraceContext does not propagate through reactive context properly in 3.1.6 / 3.2.0 #38593
Labels
for: external-project
For an external project and not something we can fix
status: duplicate
A duplicate of another issue
When using webflux in conjunction with open-telemetry with micrometer context propagation, it is expected that the trace context should be accessible throughout the controller. However, after updating to 3.1.6 (or 3.2.0) the traceId is lost within the controller at various spots.
What is even more odd, is simply adding a
@RequestBody
param to the controller "fixes" the issue in 3.1.6 / 3.2.0.Run the attached demo application and using postman or similar, call the endpoints using header (or any valid traceparent syntax header):
In 3.1.5, the traceId will always be available. In 3.1.6 the traceId will not be available in the below root endpoint -- but in the /body endpoint it will be available.
As far as I can tell (via downgrading micrometer, otel-bridge, netty, etc when using spring-boot 3.1.6/3.2.0) the issue does not seem to come from a lower level library.
demo.zip
The text was updated successfully, but these errors were encountered: