Micrometer to OpenTelemetry bridge native build warns that "OpenTelemetryMeterRegistry" does not support reading measurements #49573
Description
Describe the bug
Hey, I appreciate this may be a question rather than a bug, in which case simply close it. But I still feel it is something that should be checked. I have created app with the Quarkus Micrometer To OpenTelemetry bridge and during the native build I get warning from the OpenTelemetryMeterRegistry. What does it mean, is there something that is not supported in native? Because I did check https://quarkus.io/guides/telemetry-micrometer-to-opentelemetry and there is not a note about native mode limitations.
I does not happen for standalone Quarkus OpenTelemetry extension, only for the bridge.
Expected behavior
Native limitations are documented or warnings that are not true are avoided (if possible, even upstream?) or documented as non-actionable.
Actual behavior
I get warning:
Build resources:
- 26.49GB of memory (42.6% of 62.23GB system memory, determined at start)
- 22 thread(s) (100.0% of 22 available processor(s), determined at start)
13:21:51,893 WARNING [io.ope.ins.mic.v1_.OpenTelemetryMeterRegistry] OpenTelemetry metrics bridge does not support reading measurements
How to Reproduce?
Steps to reproduce this behavior:
quarkus create app -x=quarkus-micrometer-opentelemetry
cd code-with-quarkus/
mvn clean install -Dnative
Output of uname -a or ver
Fedora 41
Output of java -version
Temurin 21
Quarkus version or git rev
999-SNAPSHOT, 3.25.3
Build tool (ie. output of mvnw --version or gradlew --version)
Maven 3.9.9
Additional information
No response