Pro plan from £5 per endpoint per month · see pricing
Secronyx
In the next releaseLinux

ActiveMQ Artemis

See which queues are deep and whether anything consumes them, how close the broker is to its memory and disk limits, which addresses are paging and whether the cluster connection is up, with a login that can only read. This plugin is in the next Secronyx release; the current download does not include it yet.

What it answers

Questions an on-call engineer asks, which an AI client can answer with this plugin.

  • Which queues have the most messages waiting, and do they have any consumers?
  • Is the broker close to its memory or disk limit, so that producers block?
  • Is this broker the active one or a backup?
  • Which addresses are paging, or receive messages that no queue is bound to take?
  • Is the cluster connection started, and are messages to the other brokers backing up?
  • Can the monitoring login only read, with no way to destroy a queue or read a message?

What it returns

Each of the plugin's read-only tools, described in words.

  • ActiveMQ Artemis queues, one row each - messages waiting, consumers, delivering, scheduled, added, acknowledged, expired and killed counts, oldest message age, dead letter address
  • ActiveMQ Artemis broker totals - version, uptime, active or backup, memory and disk usage against their limits, connections, consumers, messages waiting and failed logins
  • ActiveMQ Artemis addresses, one row each - routing types, messages waiting in its queues, messages routed and not routed to any queue, memory used against its limit, and whether it is paging or paused
  • ActiveMQ Artemis cluster connections, one row each - whether it is started, node ID, load balancing mode, static connectors or discovery group, messages pending acknowledgement

At a glance

Plugin
artemis 1.0.0
Publisher
levantar
Platforms
Linux

Tested on

  • ActiveMQ Artemis 2.37.0 on Linux (Ubuntu 24.04, Docker), test lab

How it logs in

Without an explicit choice, install tries the methods that need no secret first, in this order.

  • A user name and password

The least-privilege login

The setup file in the pack. secronyx plugin setup artemis prints it; an administrator applies it by hand.

<!-- The least-privilege login for the artemis plugin: a user whose only role, secronyx-read, may read management attributes of the broker's own MBeans (get* and is*) and nothing else. It cannot run a management operation (destroy a queue, remove or send messages, stop the broker), set an attribute, or list or browse messages, and it cannot read a queue's first message (the FirstMessageAsJSON attribute holds its headers and body). The privilege check asks the broker and refuses a login that can. Artemis's own role (amq, or the one given to `artemis create --role`) can do all of that, and a login with it is refused. 1. etc/management.xml: inside <role-access>, in the <match domain="org.apache.activemq.artemis"> element, add secronyx-read to the roles of the get* and is* lines and add the getFirstMessageAsJSON line (an exact method name wins over a pattern), as below. Keep your own roles where "amq" stands. Leave <default-access> alone: with no role there, the login cannot read other MBeans (JVM system properties, say). 2. etc/artemis-users.properties, with a long random password (or `artemis user add`, which stores it hashed): {{user}} = CHANGE-ME etc/artemis-roles.properties: secronyx-read = {{user}} Give the user no other role. With only this role it has no rights in the broker's <security-settings>, so it cannot send or consume. 3. etc/artemis.profile: add the role to the ones the web console lets in: HAWTIO_ROLE='amq,secronyx-read' 4. etc/jolokia-access.xml allows requests whose Origin is the console's own address (*://localhost* by default). If the agent reaches the console under another name, add an <allow-origin> for it. 5. Restart the broker (management.xml and artemis.profile are read at start). --> <match domain="org.apache.activemq.artemis"> <access method="list*" roles="amq"/> <access method="getFirstMessageAsJSON" roles="amq"/> <access method="get*" roles="amq,secronyx-read"/> <access method="is*" roles="amq,secronyx-read"/> <access method="set*" roles="amq"/> <access method="browse*" roles="amq"/> <access method="count*" roles="amq"/> <access method="*" roles="amq"/> </match>

See it run

Terminal recording from the test lab: artemis-linux-harness
A real run on the shared test lab.

Read-only, in layers

Every request is a GET or HEAD to the endpoint the operator configured, on a path fixed in the signed pack. Redirects are not followed, and requests known to change state are refused.

These controls narrow what the plugin can do; none of them is a guarantee on its own. An administrator can still accept a more powerful login on purpose (audited and shown in status), root or Administrator on the host can replace the agent, and the plugin can read whatever its login can see.