I'm trying to introduce OpenTelemetry into our existing Quarkus-based (v 2.9.2.final) set of services. All services are written in a reactive way based on Mutiny. I'm failing to continue Spans or add events and attributes to them. I have configured Quarkus to produce traces into a locally running Otel collector with Zipkin and Jaeger.
Observations:
- Quarkus creates Spans for every incoming REST request. I can add attributes here. Such span gets reported into Jaeger.
- If I use
@WithSpan
annotation on a reactive method somewhere downstream - this span gets reported but without the link to the parent span created in the REST API - If I do not annotate the downstream reactive method and try to access and amend
Span.current()
I'm provided with the span created in the REST API abut any attribute or event addition is not propagated to Jaeger - If I try to inject OpenTelemetry
Context
bean - there is no such
Is there any working Quarkus OpenTelemetry reactive code sample? Or does Quarkus support OpenTelemetry just partially in non-reactive code?