sudoit1/rahdar repository overview

⁠Rahdar

One open-source console for your Apache ActiveMQ® Artemis, Apache Kafka® and RabbitMQ clusters.

One instance, every cluster you run, in one estate: health judged on one scale and every backlog in one table, Artemis queues, Kafka consumer groups and RabbitMQ queues side by side. Kafka lag is shown as the estimate it is, with its per-partition breakdown. Nothing destructive runs before its preview, and where the approval gate is on, a second person approves it.

• Apache Artemis 2.33.0 and later: live/backup topology with HA roles polled from every node, cross-node queues and addresses, message flow, safe message operations, request-reply tracing and SQL over your messages.
• Apache Kafka 2.8 and later, KRaft and ZooKeeper mode: consumer, share and classic groups with per-partition lag, previewed offset resets, topic configuration, ACLs, hanging transactions, brokers and the controller quorum.
• RabbitMQ 3.13 and later (4.x tested): nodes with their alarms and partitions, virtual hosts, bindings, policies, permissions, shovels and federation, classic, quorum and stream queues, and streams browsed by offset.

It works against your existing brokers. Register an Artemis cluster from one management URL, a Kafka cluster from its bootstrap servers, or a RabbitMQ cluster from its management URLs; nothing here starts or reconfigures a broker.

Extend it with plugins, installed from the UI: screens, API, assistant tools and data of their own, most without a restart. When a plugin needs one, Rahdar restarts itself if the container has a restart policy — the compose file sets RAHDAR_PLUGINS_RESTART_SUPERVISED=true beside restart: unless-stopped.

Documentation: rahdar.dev⁠ (Kafka guide⁠, RabbitMQ guide⁠)  ·  Source and issues: github.com/sudoitir/rahdar⁠

Every image is signed by the project's release workflow and carries SLSA provenance and a CycloneDX SBOM: verify a release⁠.

⁠Screenshots

Every cluster in one estate: Artemis and Kafka side by side, the worst backlog first.

Kafka lag is an estimate, and opens to every partition, slowest first.

A consumer group's lag per partition and its members.

An offset reset is previewed per partition before it is held to confirm.

A hanging transaction, found and aborted with its reach stated first.

Registration checks every broker on the address it advertises.

Artemis topology, with HA roles polled from every node.

⁠Run it

Rahdar and its Postgres. Your Artemis, Kafka and RabbitMQ clusters already exist and are registered through the UI — nothing here starts a broker.

base=https://raw.githubusercontent.com/sudoitir/rahdar/main/deploy/compose
mkdir -p rahdar/compose rahdar/postgres && cd rahdar/compose   # the compose file mounts ../postgres
curl -sO "$base/compose.prod.yaml"
for f in postgresql.conf 10-pg-stat-statements.sql; do curl -s "${base%/compose}/postgres/$f" -o "../postgres/$f"; done
curl -s "$base/.env.example" | sed \
  -e "s|^SECRET_KEY=.*|SECRET_KEY=$(openssl rand -base64 32)|" \
  -e "s|^DB_PASSWORD=.*|DB_PASSWORD=$(openssl rand -hex 24)|" > .env
docker compose -f compose.prod.yaml --env-file .env up -d

The sed fills in a fresh secret key and database password; every other setting in .env has a working default. The table below lists what the container reads.

Or a bare container against your own Postgres:

docker run -p 8080:8080 \
  -e RAHDAR_DB_URL=jdbc:postgresql://db:5432/rahdar \
  -e RAHDAR_DB_USER=rahdar \
  -e RAHDAR_DB_PASSWORD=... \
  -e RAHDAR_SECRET_KEY="$(openssl rand -base64 32)" \
  sudoit1/rahdar:dev

First login. Username admin. The first run against an empty database generates the password and prints it once to the container log:

docker compose -f compose.prod.yaml logs rahdar | grep -A4 'Created administrator'

At the first sign-in you choose your own password and set up two-step verification, which the admin role requires. An administrator who has lost both their device and their recovery codes is recovered with the break-glass RAHDAR_IDENTITY_LOCAL_RECOVER (configuration guide⁠).

Reverse proxy. The live UI stream is SSE at GET /api/v1/stream; a proxy in front of Rahdar must not buffer it (nginx proxy_buffering off;, Apache no output buffering on that path; Traefik works as-is). Without this the topology graph and queue grid only update on the 5-second poll.

⁠Tags

linux/amd64 and linux/arm64. Versioning is CalVer and the number carries no compatibility promise — a release's breaking changes are listed at the top of its release notes⁠.

⁠Licence

Apache-2.0.

Apache, Apache Kafka, Kafka, Apache ActiveMQ, ActiveMQ and Artemis are trademarks of the Apache Software Foundation; RabbitMQ is a trademark of its owner. Rahdar is not affiliated with or endorsed by them; the names describe what the software works with.