open-telemetry / open-telemetry/opentelemetry-java-instrumentation
Why was the fix in #15011 only needed for `MicrometerBridgeAutoConfiguration`?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.6k
- Forks
- 1.2k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 228
Description
Why was the fix in #15011 only needed for MicrometerBridgeAutoConfiguration but not for https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/instrumentation/spring/spring-boot-autoconfigure/src/main/java/io/opentelemetry/instrumentation/spring/autoconfigure/internal/instrumentation/mongo/MongoClientInstrumentationAutoConfiguration.java or the other configuration classes.
Originally posted by @laurit in https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/15011#issuecomment-3411579122
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 comparing the fix in issue #15011 with MicrometerBridgeAutoConfiguration and the referenced MongoClientInstrumentationAutoConfiguration.java file, then inspect the other configuration classes mentioned in the issue. Determine why the fix applies only to MicrometerBridgeAutoConfiguration; the issue is done when that distinction is explained clearly, with any needed documentation identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend, observability-sre
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100