Micrometer to OpenTelemetry Bridge

[brunobat]

solves #43621

The implementation uses the opentelemetry-micrometer-1.5 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:

• Native tests
• Tests with exemplars using OTel Tracing.
• Documentation updates
• Decide what to do with the OTel metrics auto instrumentation
• Move the code to the OTel extension? No.
• Disable x.histogram in DistributionSummary
• Silence io.ope.ins.mic.v1_.OpenTelemetryMeterRegistry] (main) A MeterFilter is being configured ...
• Enable otel metrics and disable otel metrics instrumentation

[quarkus-bot]

/cc @ebullient (micrometer)

[github-actions]

🙈 The PR is closed and the preview is expired.

[brunobat]

@radcortez I wonder why this didn't work here... I had to set these properties in the runtime application.properties

[brunobat]

Thanks @geoand :)

[geoand]

🙏🏽

[brunobat]

rebased

[brunobat]

There's something wrong with the branch... It's not piking up the conflicts on native-tests.json.
Do not merge.

[brunobat]

All good after all. Holly's native-tests.json reorg is not on main and I got confused.
@gsmet are you ok with this one being merged?

[gsmet]

I added a few minor suggestions, questions, mostly to the doc.

I would recommend fixing all the easy stuff before merging and then we can discuss the remaining points after merge if they require some discussion.

[brunobat]

Addressed the review @gsmet

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit a6c8a69.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit a6c8a69.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

---

Flaky tests - Develocity

⚙️ JVM Tests - JDK 17

📦 extensions/micrometer/deployment

✖ io.quarkus.micrometer.deployment.binder.VertxHttpClientMetricsTest.testWebClientMetrics - History

• event executor terminated - java.util.concurrent.RejectedExecutionException

java.util.concurrent.RejectedExecutionException: event executor terminated
	at io.netty.util.concurrent.SingleThreadEventExecutor.reject(SingleThreadEventExecutor.java:934)
	at io.netty.util.concurrent.SingleThreadEventExecutor.offerTask(SingleThreadEventExecutor.java:353)
	at io.netty.util.concurrent.SingleThreadEventExecutor.addTask(SingleThreadEventExecutor.java:346)
	at io.netty.util.concurrent.SingleThreadEventExecutor.execute(SingleThreadEventExecutor.java:836)
	at io.netty.util.concurrent.SingleThreadEventExecutor.execute0(SingleThreadEventExecutor.java:827)
	at io.netty.util.concurrent.SingleThreadEventExecutor.execute(SingleThreadEventExecutor.java:817)
	at io.vertx.core.impl.EventLoopExecutor.execute(EventLoopExecutor.java:35)

[gsmet]

I just saw this had the backport label, I don't think we can backport it, it's too much of a change, it's going to be for 3.19.

[brunobat]

That's fine.