-
Story
-
Resolution: Done
-
Optional
-
None
-
False
-
-
False
-
+
-
---
-
-
solves https://github.com/quarkusio/quarkus/issues/43621
The implementation uses the [opentelemetry-micrometer-1.5](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/micrometer/micrometer-1.5/library) library.
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 from the `quarkus-opentelemetry` extension and will use it's configuration and exporters.
`quarkus-micrometer` extension configurations should also work, as verified on some tests.
Missing:
- [x] Native tests
- [ ] Tests with exemplars using OTel Tracing.
- [x] Documentation updates
- [x] Decide what to do with the OTel metrics auto instrumentation
- [x] Move the code to the OTel extension? No.
- [x] Disable x.histogram in DistributionSummary
- [x] Silence `io.ope.ins.mic.v1_.OpenTelemetryMeterRegistry] (main) A MeterFilter is being configured ...`
- [x] Enable otel metrics and disable otel metrics instrumentation