Micrometer to OpenTelemetry Bridge #43831
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/cc @ebullient (micrometer) |
|
🎊 PR Preview 8f50794 has been successfully built and deployed to https://quarkus-pr-main-43831-preview.surge.sh/version/main/guides/
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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-opentelemetryextension and will use it's configuration and exporters.quarkus-micrometerextension configurations should also work, as verified on some tests.Missing: