Artemis StudioOne console for every Artemis cluster

Live topology, cross-node queues, safe message operations, and SQL over your messages — across every Apache ActiveMQ Artemis cluster you run, from one instance.

Quickstart

What it is

GitHub

The whole cluster, not one broker

Live/backup pairs, replication state and a shared-NodeID axis on one canvas. HA role is polled from every node, never read from config — two live in a pair is a split-brain alert, not a surprise at 3am.

Every queue, every node, one table

Queues, addresses, consumers, sessions, connections and producers across the estate in a single virtualised grid, updating over SSE. Sort by depth and the worst thing in the cluster is the first row.

SQL over your messages

"Where did order 4471 go?" is one query across every queue in the cluster — including the body, which a JMS selector cannot see. The cost of the query is shown before it runs.

Destructive operations you can trust

Every mutating call takes ?dryRun=true and answers with the affected count without acting. Purge and delete need the queue's name typed. Everything is audited in the same transaction as the command.

Request-reply tracing

Correlate a request to its reply across addresses and nodes, with latency and timeout statistics against expectations you declare. Broker clocks are normalised onto Studio's, and the skew is disclosed.

An MCP server over the same grants

Ask an assistant why ORDERS.DLQ is backed up and have it answer against your real clusters — through a dozen intent-shaped tools, under the same permissions and the same audit trail as a person.

See it working

Artemis Studio: topology, the cross-node queue grid, and a dead-lettered message

A real session against a real cluster pair: the topology, the cross-node queue grid, and a message that went to the dead-letter queue.

Install it in one command

bash

git clone https://github.com/sudoitir/artemis-studio && cd artemis-studio
just up          # Studio + Postgres, secrets generated, pinned to the latest release

Your brokers already exist — Studio registers them, it does not start them. It works against an unmodified broker.xml beyond the management endpoints you almost certainly already run. Full quickstart →

Alpha

Under active development and not yet feature-complete. Published images are pre-stable dev builds (sudoit1/artemis-studio:dev, no :latest yet). Expect breaking changes.