SpringBoot Fine grained enabled/disable on different Tracers.

In situation where you want to use a different implementation in dev/prod. For example Zipkin in local machine and OTLP in production. The current AutoConfiguration classes use @ConditionalOnEnabledTracing which enables/disables all of them.

Does it make sense to add management.zipkin.tracing.enabled, management.otlp.tracing.enabled?

Comment From: philwebb

We're not too keen to add too many enabled poroperties, and in this case it's slightly unusual to switch tracing backends in different environments.

We recommend directly disabling the auto-configuration classes if you want to do this. Something like:

spring.autoconfigure.exclude=org.springframework.boot.actuate.autoconfigure.tracing.OpenTelemetryAutoConfiguration

and

spring.autoconfigure.exclude=org.springframework.boot.actuate.autoconfigure.tracing.BraveAutoConfiguration

Depending on which one you want to disable.