Micrometer to OpenTelemetry bridge in Quarkus

[guillaumBrisard]

Description

This feature to follow the next step after Add support for OpenTelemetry metrics
I will just quote @brunobat

In relation to the automatic instrumentation, for now, we only plan a bridge from the current metrics implemented with Micrometer to OpenTelemetry format. The semantic conventions to use (the names of the attributes in metrics) will be the ones coming from Micrometer. There are many reasons for this, I can highlight a few:

• Micrometer conventions are quite stable and currently, OpenTelemetry Semantic conventions are still being created and change quite frequently.
• There are many projects already instrumented with Micrometer and very few using OpenTelemetry metrics.

Is there a roadmap ?

Implementation

See comment bellow.

No response

[quarkus-bot]

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

[brunobat]

Thanks for creating the issue. I might update the description in the future to include more details.
I plan to work on this until the end of the year.
The Observability roadmap is on this development mailing list group thread: https://groups.google.com/g/quarkus-dev/c/y5-ojIVsa_M/m/4wquJi4bBQAJ

[brunobat]

The implementation uses the opentelemetry-micrometer-1.5

This allows us to create a Micrometer registry implemented with the OpenTelemetry SDK and APIs.

All telemetry data created with both Micrometer and OpenTelemetry will be processed by the same OpenTelemetry SDK instance and will use it's configuration and exporters.

See: Micrometer to OpenTelemetry Bridge #43831

[brunobat]

Fixed by #43621