Skip to main content
Netdata provides real-time, high-resolution system metrics (CPU, RAM, disk, network, per-container) for each node. It is the default server-metrics service on standard and high compute tiers. Netdata is served at netdata.<domain>.

​
When you get it

Netdata is enabled by the resolver on standard/high tiers. On low-resource nodes the resolver uses lighter tools (Beszel or Glances) instead.
stack-spec.yaml
stackkit: base-kit
# Netdata is enabled by default on standard/high tiers — no config needed.

​
Steps

1

Open Netdata

Open https://netdata.<domain> to see live per-node dashboards.
2

Review key charts

Check CPU, memory pressure, disk I/O, and per-container resource usage.
3

Set alarms

Tune Netdata’s built-in health alarms for the thresholds you care about.

​
Verify

  • Live charts update at netdata.<domain>.
  • Per-container metrics appear for your running services.

​
Next steps

Uptime Kuma

Add uptime checks and status pages.

Tool alternatives

Compare Netdata, Beszel, and Glances.

​
Troubleshooting

Verify the Netdata container is running (docker logs netdata) and that the host has access to /proc and /sys.