pharn-dev/argus

Investigate slow requests, event-loop stalls, GC pressure, and stream backpressure using Argus data. Use for a runtime incident or alert that needs evidence-backed hypotheses and a next experiment.

Investigate Node.js memory growth with Argus raw samples, allocation sites, and heap snapshot summaries or diffs. Use for suspected leaks, rising RSS, or determining what memory grew.

Create and replay Argus collector alerts or sandboxed diagnostic rules from an observed Node.js runtime problem. Use when defining a threshold, sustained condition, or custom diagnostic finding.

Install, connect, and verify Argus diagnostics in a Node.js application. Use when adding Argus, configuring agent output, or repairing the agent-to-collector-to-dashboard connection.

Verify a Node.js performance or memory fix by comparing Argus measurements before and after the change. Use when deciding whether a runtime change helped, regressed, or remains inconclusive.