Difference between opentelemetry-spring-boot-starter and the OpenTelemetry support in micrometer

[silver-mx]

I am trying to find out the easiest and most reliable way to enable OpenTelemetry observability in SpringBoot. On one hand we have the OpenTelemetry micrometer support for metrics and tracing. Tracing requires an exporter provided by OTEL as well:

    <dependency>
        <groupId>io.opentelemetry</groupId>
        <artifactId>opentelemetry-exporter-otlp</artifactId>
    </dependency>

On the other hand, we have the official OpenTelemetry starter dependency opentelemetry-spring-boot-starter which does autoconfiguration, instrumentation and brings several additional dependencies not included by default in SpringBoot.

To the best of my knowledge there is some overlapping in both solutions as they do instrumentation to some degree, but I would like to know the following:

1. What offers opentelemetry-spring-boot-starter that micrometer + opentelemetry-exporter-otlp does not already have.
2. In which scenarios I would choose opentelemetry-spring-boot-starter instead of the micrometer support.

NOTE: I posted the same question in StackOverflow but nobody has answered it, so I thought trying here.

[trask]

hi @silver-mx!

At a very very high level:

OpenTelemetry Spring Boot starter

• Natively uses the OpenTelemetry API, OpenTelemetry SDK and the OpenTelemetry semantic conventions
• Supported by the OpenTelemetry community (governed by the CNCF / Linux Foundation)

Micrometer

• An independent standalone observability system
• Offers optional bridges into parts of the OpenTelemetry ecosystem
• Supported by the Micrometer community (governed by Broadcom Inc)

As a member of the OpenTelemetry Java community, I (probably unsurprisingly) recommend using the OpenTelemetry Spring Boot starter. We have a great community behind it, and are continuously making improvements. If you try it out and have any problems or suggestions, please open an issue in our repository.