Why OpenTelemetry enabled by default?

[ppatierno]

May I ask why the property quarkus.opentelemetry.enabled is true by default so having the OpenTelemetry tracer being instantiated by default?
Tracing is something optional so I would expect it to be disabled by default, not the other way around.

[quarkus-bot[bot]]

/cc @brunobat (opentelemetry), @radcortez (opentelemetry)

[radcortez]

The configuration is only applied when the Quarkus OpenTelemetry Extension is added to a Quarkus project. We assume that if the user added that dependency, OpenTelemetry is required (equivalent to enabling a configuration).

On the other hand, requiring the user to add the dependency, plus enable a flag to have OpenTelemetry working, was counter-intuitive, but I guess that some users would prefer otherwise :)

[ppatierno]

I am in dev mode right now

[brunobat]

If you build each time you start devmode it will always looks like the build time property is runtime. Not quite.
Try to start the server with java -jar ... with a changed build time property value. You will see no behaviour changes.

[ppatierno]

I am usually running the app this way ...

mvn quarkus:dev -Dquarkus.args="--config-file config/application.properties"

Where the configuration is in an external application.properties file, where I have my own config params and quarkus OpenTelemetry related. Something like this.

#Bridge related settings
bridge.id=my-bridge
# uncomment one the following lines (bridge.tracing) to enable Jaeger tracing, check the documentation how to configure the tracer
# OpenTracing support
#bridge.tracing=jaeger
# OpenTelemetry support
#bridge.tracing=opentelemetry

#Apache Kafka common
kafka.bootstrap.servers=localhost:9092

#Apache Kafka producer
kafka.producer.acks=1

#Apache Kafka consumer
kafka.consumer.auto.offset.reset=earliest

#HTTP related settings
http.host=0.0.0.0
http.port=8080
#Enable CORS
http.cors.enabled=false
http.cors.allowedOrigins=*
http.cors.allowedMethods=GET,POST,PUT,DELETE,OPTIONS,PATCH

#Enable consumer
http.consumer.enabled=true

#Enable producer
http.producer.enabled=true

#Quarkus related configuration

#OpenTelemetry support
quarkus.application.name=${OTEL_SERVICE_NAME}
quarkus.opentelemetry.enabled=true
quarkus.opentelemetry.tracer.exporter.otlp.endpoint=${OTEL_EXPORTER_OTLP_ENDPOINT}

I also have a SmallRye config interceptor to "translate" things like http.port to quarkus.http.port and so on.

[ppatierno]

Thanks to @brunobat we had an offline call and not things are clearer. I need to run the application as jar and see that it won't work for me :-)

[ppatierno]

Thanks to @brunobat we had an offline call and not things are clearer. I need to run the application as jar and see that it won't work for me :-)