RocketMQ Exporter

RocketMQ Exporter is a Prometheus metrics exporter for Apache RocketMQ.

  • Monitoring & Logging
RocketMQ Exporter is a Prometheus metrics exporter for Apache RocketMQ. It collects performance and health metrics from your RocketMQ messaging system and exposes them in Prometheus format, enabling monitoring via dashboards and alerting systems.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

40/100 Fair

Maintained
20last commit 534 days ago
Popular
50325 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data
Security check
85no serious findings, tests

Based on 4 of 5 factors.

GitHub stars
325
Open issues
52
Last commit
2025-06-05
Latest release
rocketmq-exporter-0.0.2
License
Apache-2.0
Activity
stale

Checked yesterday - source: GitHub (apache/rocketmq-exporter)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Start the NameServer first Start RocketMQ's NameServer and wait for the 'boot success' message; on Windows you may need to set ROCKETMQ_HOME before running mqnamesrv.cmd. It is the lookup service, so without it the broker and rocketmq-exporter can't find where topics and brokers live. source
  • Start a broker pointed at it Start a broker with the NameServer address, for example mqbroker -n localhost:9876, then check the broker log for the 'boot success' line. The exporter needs a running broker to read RocketMQ stats from, so if this step fails your exporter will have no data. source
  • Keep port 9876 reachable The NameServer example uses port 9876, so make sure that port is open on your homelab network or change the -n address to the correct IP and port. If the broker can't reach the NameServer, it won't register and RocketMQ clients or exporters can't connect. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need the RocketMQ NameServer running before RocketMQ Exporter can work?

Yes, start the NameServer and wait for the boot success message because it is the lookup service used to find topics and brokers. Without it, the broker and exporter cannot locate where topics and brokers live.

Which port must be reachable in the local NameServer example?

The example uses port 9876 for the NameServer, so keep that port open on your network or point the broker to the correct IP and port.

Why does RocketMQ Exporter have no metrics even if the process is running?

It needs a running broker to read RocketMQ stats, so check the broker log for the boot success line before expecting exporter data.

Answers sourced from github.com, github.com

Community

Collected 49 days ago - public community threads