Using the OTel and Zipkin starters together creates invalid configuration #49183
Description
When using both spring-boot-starter-opentelemetry and spring-boot-starter-zipkin the resulting configuration breaks:
***************************
APPLICATION FAILED TO START
***************************
Description:
Parameter 1 of method propagatingSenderTracingObservationHandler in org.springframework.boot.micrometer.tracing.autoconfigure.MicrometerTracingAutoConfiguration required a single bean, but 2 were found:
- bravePropagator: defined by method 'bravePropagator' in class path resource [org/springframework/boot/micrometer/tracing/brave/autoconfigure/BraveAutoConfiguration.class]
- otelPropagator: defined by method 'otelPropagator' in class path resource [org/springframework/boot/micrometer/tracing/opentelemetry/autoconfigure/OpenTelemetryTracingAutoConfiguration.class]
I wonder if we could make one of the two aware of the other and back off or provide a better error message if we consider this an invalid combination.