Integration · Queues & brokers

NATS / JetStream

Streams, consumers, slow consumer detection.

What gets collected

The NATS monitoring port plus the JetStream API. Metrics: stream throughput, pending messages, consumer ack lag.

Requirements

  • NATS 2.x + JetStream
  • monitoring port -m :8222

Key metrics

Collected out of the box. Every metric is available in dashboards, alerts and PromQL.

nats.stream.throughputnats.pending.msgsnats.consumer.ack_lagnats.slow_consumers

Setup steps

  1. 1NATS server with -m :8222
  2. 2JetStream enabled
  3. 3Optional: connect via nats-mon

After install

  • · Metrics show up on the dashboard within 15-30 seconds
  • · Integration labels flow into filters automatically
  • · Dashboard presets for common metrics are available in the editor
More in the docs
NATS / JetStream
Open the guide →

Frequently asked questions

What does Unimoni collect from NATS / JetStream?
Streams, consumers, slow consumer detection. Every metric lands in the same TSDB as the rest of your stack, so you can build dashboards and alerts across NATS / JetStream and everything else in one place.
How long does it take to connect NATS / JetStream?
Usually a few minutes: a handful of steps, no code changes. Metrics show up on your dashboards within 15–30 seconds of the first scrape.
What access does the NATS / JetStream integration need?
Only the minimum listed under Requirements above — a scoped token or role, nothing more. Unimoni asks for the least privilege each system supports.
Is NATS / JetStream monitoring available self-hosted and on the free plan?
Yes. Every integration works identically on Unimoni Cloud and self-hosted, and is included from the free tier up.

Similar integrations