NATS
See whether NATS has had slow consumers and which clients it disconnected and why, which JetStream consumers have messages pending, and whether the cluster routes are up, through read-only requests to the monitoring port. 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.
- Has the server disconnected any slow consumers, and which clients were they?
- Which connections have the most bytes waiting to be sent, or have gone idle?
- Which JetStream consumers are falling behind, and are their messages being acknowledged?
- Is this server routed to every other server in the cluster?
- How close is JetStream to its memory and storage limits?
- Which NATS version is running, and since when?
What it returns
Each of the plugin's read-only tools, described in words.
- NATS server in one row - version, cluster, start time, client and route counts, slow consumers, message totals, memory, CPU, payload and pending limits, and JetStream memory and storage use
- NATS client connections - address, client name and library, activity, round trip time, bytes pending, message counts and subscriptions; closed ones say when and why, such as a slow consumer
- NATS JetStream consumers on this server - stream, name, messages pending, unacknowledged and redelivered, waiting pulls, and the last delivered and acknowledged sequence and time
- NATS cluster routes from this server - remote server name and ID, address, configured or solicited, activity, round trip time, bytes pending, message counts and pinned account
At a glance
- Plugin
- nats 1.0.0
- Publisher
- levantar
- Platforms
- Linux, Windows, macOS
Tested on
- NATS Server 2.10.29 on Linux (Ubuntu, Docker), CI runner
- NATS Server 2.10.29 on macOS (official release), CI runner
- NATS Server 2.10.29 on Windows Server (official release), CI runner
How it logs in
Without an explicit choice, install tries the methods that need no secret first, in this order.
- No login (a local endpoint)
Least privilege
The setup file in the pack. This plugin needs no password and creates no login: the file says what it needs on the host and how to keep that to the minimum.
See it run
Recording coming. Install, setup and status runs for this plugin are recorded on the shared test lab, and appear here once they have run.
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.