Disk, memory, and CPU monitoring is configured

NIST AU-6 requires continuous review of audit records and system performance. For self-hosted deployments, memory leaks, disk-filling log files, and CPU runaway are the most common causes of unexpected outages — and they are invisible without infrastructure-level monitoring. A Node.js process with a memory leak gradually degrades over hours until OOM kills it; without a memory usage alert, the first signal is the application going down. This check applies only to self-hosted deployments because serverless platforms (Vercel, Netlify, Cloudflare Workers) manage infrastructure scaling automatically and do not expose these metrics as meaningful operator concerns.

Configure infrastructure metrics collection appropriate to your hosting environment.

For Fly.io, enable Prometheus metrics export in fly.toml:

[metrics]
  port = 9091
  path = "/metrics"

Then view metrics in the Fly.io dashboard under your app's Metrics tab.

For Docker or VPS deployments, install the Datadog agent:

DD_API_KEY=<your-key> bash -c "$(curl -L https://s3.amazonaws.com/dd-agent/scripts/install_script_agent7.sh)"

This collects CPU, memory, and disk metrics automatically and surfaces them in the Datadog infrastructure dashboard.

For Railway, use the built-in metrics view in your service's Metrics tab — no configuration needed.