Troubleshoot NATS

When to use this skill

• Slow consumer cascade: A subscriber falls behind then server disconnects it then
• File descriptor exhaustion: Connection count hits OS ulimit -n. No new
• JetStream Raft instability: Network latency or GC pauses cause Raft
• Memory pressure / OOM: Slow consumers buffering in memory, large subscription
• Silent message loss (core NATS): Publisher sends to subject with zero
• Any time the user reports a NATS service behaving outside its expected envelope (elevated errors, latency, saturation, resource exhaustion, or unexpected restarts).
• An on-call engineer is paging on a Netdata alert tied to a NATS instance and wants a structured triage path.

Key facts