Artemis Studio: an open-source cluster console for ActiveMQ Artemis

Description and use

Artemis Studio consolidates ActiveMQ Artemis cluster monitoring into a single interface, offering live topology, a unified queue table, message content search, flow visualization, safe operations, and configuration review.

Problem

The default Artemis console manages one broker at a time, requiring a separate tab per node and manual JMX navigation to locate queues such as ORDERS.DLQ, which is inefficient for cluster-wide monitoring.

Outcome

Artemis Studio consolidates cluster monitoring into a single interface, reducing manual effort and providing advanced features such as live topology, unified queue listing, message content search, flow visualization, safe operations, and configuration review.

Workflow

• Clone the repository: git clone https://github.com/sudoitir/artemis-studio
• Navigate into the project directory: cd artemis-studio
• Start the application with Docker Compose: docker compose up

Evidence

The console that ships with Artemis manages one broker at a time. You open a tab per node and walk a JMX tree until you find it.

Source

Live topology with HA roles polled from the nodes themselves

Source

Every queue on every node in one table, sorted by depth

Source

Search over message contents, with a cost indicator that tells you whether a query is a cheap header lookup or a full body scan

Source

Message flow view across diverts, bridges and cluster hops

Source

Safe operations: dry-run on mutating calls, and you type the resource name to confirm a purge or delete

Source

Setup review that flags known misconfigurations

Source

Brokers are polled with one batched Jolokia request per node, tiered by how often data changes, with a rate limiter so the console doesn't load the brokers it watches.

Source

It's alpha, so expect breaking changes. Apache-2.0, and not affiliated with the ASF.

Source