open-telemetry / open-telemetry/opentelemetry-java-instrumentation
add support for ActiveMQ Artemis JMX metrics
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.6k
- Forks
- 1.2k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 228
Description
Currently, setting otel.jmx.target.system to activemq allows to capture JMX metrics of an ActiveMQ classic instance.
ActiveMQ provides two separate implementations:
- ActiveMQ Classic which is the historical/legacy version but still updated, latest is 6.x
- ActiveMQ Artemis which is the newer version, latest version is 2.x
Due to the differences in the underlying architecture it is likely that the Classic and Artemis metrics will be different, they could however be defined in the same yaml if there is no overlap.
This is a follow-up of #14278
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 at the otel.jmx.target.system configuration and review the existing ActiveMQ Classic coverage, along with the context in follow-up #14278. Identify the Artemis JMX metrics that need support and verify that the completed work captures Artemis metrics without breaking Classic coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100