The ConfigValue
instance for quarkus.otel.sdk.disabled
is null during relocation
#33493
Labels
Milestone
While porting our Strimzi HTTP bridge from Quarkus 2.x to 3.x, I found a potential issue around the
quarkus.otel.sdk.disabled
property.Let me set the use case first ... with Quarkus 2.x.
In our bridge we are currently using a
bridge.tracing=opentelemetry
property to enable/disable OpenTelemetry. We know that it's not possible enable/disable tracing at runtime with Quarkus 2.x and together with @brunobat we came with a workaround about just disabling the sampler to avoid sending traces. It was done by using a configuration relocator interceptor like this one here. The relocator purpose is to take backward compatibility (user still needs to set or notbridge.tracing
property).When moving to Quarkus 3.x we have the
quarkus.otel.sdk.disabled
property which allows to enable/disable tracing at runtime so the "sampler" workaround is not needed anymore.Following the same logic I was going to relocate that property via our own
bridge.tracing
but when the following snippet of code runs, thequarkus.otel.sdk.disabled
result to be null.I am just following the same logic as before but using the
quarkus.otel.sdk.disabled
instead of thequarkus.opentelemetry.tracer.sampler
which is not null and works fine.The text was updated successfully, but these errors were encountered: