open-telemetry / open-telemetry/opentelemetry-java-instrumentation
Failed to collect dubbo metrics by micrometer instrumentation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.6k
- Forks
- 1.2k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 228
Description
I am using dubbo sdk in my project, so i want to collect dubbo sdk to otel agent metrics using "prometheus/9464", so i set the config
-Dotel.instrumentation.micrometer.enabled=true
-Dotel.instrumentation.spring-boot-actuator-autoconfigure.enabled=true
but when i curl http://localhost:9464/metrics there are no dubbo metrics, and when i curl http://localhost:8080/actuator/metrics the dubbo metrics are disappeared(when i remove the agent, it will go back)
Is this a bug? Or a feature? How can i collect the dubbo metrics to my agent?
Agent Version: 2.26
System: Macos
JDK: 21
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 reproducing the reported setup with Java 21, agent version 2.26, the Micrometer and Spring Boot Actuator configuration, and the Dubbo SDK. Compare /metrics on port 9464 and /actuator/metrics on port 8080 with and without the agent; done means determining whether the missing Dubbo metrics are an instrumentation bug or unsupported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, prometheus
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100