quarkus.jaeger.enabled cannot be changed at runtime

[Den]

Hello,

the `quarkus.jaeger.enabled ` is a build time one:

Build time property cannot be changed at runtime:
 - quarkus.jaeger.enabled was 'false' at build time and is now 'true'

Is there any technical reason for that? I'd like it to be selectively enabled at runtime.

Thanks!

[Roberto Cortez]

Hi Den,

Usually, the build time configuration allow us to selectively remove (or not include stuff).

Please, open an issue on GH, so we have look at it. Thanks!

Cheers,

Roberto

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/c500fbcb-aac5-41ae-afc5-3a86d7743356n%40googlegroups.com.

[Loïc MATHIEU]

Hello Den,

quarkus.jaeger.enabled is a build time property so you can only switch it at test or during dev mode, as soon as you package your application as a jar or a native apps the value from the build is used.

I don't remember why and didn't had the time to look at the code so I don't know why it's a build time but there should be a strong reason.

However, if you don't configure the jaeger host, a noop tracer is used, effectively disabling open tracing.

Hope it helps,

Loïc

--