• configure OpenTelemetry via opentelemetry-sdk-extension-autoconfigure
  • use opentelemetry-micrometer-1.5 bridge
  • the change is not fully backwards compatible, which could be improving by having new auto config classes - should be discussed
  • all spring config options are still respected, both providing beans (e.g. for span filtering) and application properties
  • if the user does not configure settings explicitly in application properties, then the SDK auto-configuration is used, for example you can either use management.tracing.propagation or otel.propagators - not sure if this can be surprising
  • both sdk autoconfig and opentelemetry-micrometer-1.5 are alpha in otel, but haven't had any incompatible changes in the last months - I'll ask about it in the Java SIG

Comment From: pivotal-cla

@zeitlinger Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

Comment From: wilkinsona

Thanks for the proposal, @zeitlinger. Unfortunately, moving to an OpenTelemetry alpha is a non-starter. We'd also like to let other related changes settle before considering any further changes in this area. Those changes are coming in Micrometer, Micrometer Tracing and https://github.com/spring-projects/spring-boot/pull/34508 and should all be available in 3.1.0-M2 that is to be released later this month.