open-telemetry / open-telemetry/opentelemetry-java-instrumentation
Getting Micrometer Metrics Bridge from Alpha to Stable
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.6k
- Forks
- 1.2k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
I opened this issue to track the work that is needed in order to get the Micrometer Metrics Bridge from the alpha status to stable.
Up until the latest release (2.16.0), the instrumentation was using a class from an incubating API. That was removed in https://github.com/open-telemetry/opentelemetry-java-instrumentation/commit/b3233c4203603a7e3860cc4429da1e858ac67838, so there is no more dependencies on alpha libraries from what I can see.
Describe the solution you'd like
I'm not sure what is needed to get this instrumentation to the stable state, but I'm available to help out getting there.
Describe alternatives you've considered
No response
Additional context
@brunobat perhaps you have some inputs on this from Quarkus?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Micrometer Metrics Bridge instrumentation and the linked commit that removed its incubating API dependency. Determine which criteria and project changes are required for stable status, including any relevant Quarkus input; the work is done when those requirements are agreed and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100