Host metrics panels

Open any server from the Servers page to get its metrics view: a status bar with live gauges on top, then a grid of chart panels. Data arrives from the collector once a minute, so every chart has per-minute detail for recent ranges.

The status bar and summary

The top of the page answers “is this server OK right now”:

• Status — Online, or Offline once the collector stops reporting.
• LAST CHECKED — when the most recent batch arrived.
• UPTIME — time since boot; hovering shows the exact boot time. A warning icon appears next to it when the server has a pending reboot (the flag Ubuntu and Debian set after kernel or libc updates).
• Four gauges: CPU (with the model, core count, architecture, current frequency, and temperature underneath), RAM, Swap, and Disk (the root filesystem).
• Server details: hostname, OS, kernel, private and public IP, location, and provider. Location and provider are derived from the public IP — the collector doesn’t collect them (what it does send).

Reading a chart panel

All chart panels share the same controls:

• Time range — buttons from 3H to 90D (3H, 6H, 12H, 24H, 7D, 30D, 60D, 90D) in the page header apply to every panel at once. Recent ranges draw per-minute points; ranges that reach further than about a month back draw hourly averages, so long-range charts look smoother than short-range ones.
• Cur / Avg / p95 / Max — a stats row under each chart, computed from exactly the points the chart is showing. Change the range and the stats follow.
• Refresh — the page header has a refresh-now button and an auto-refresh interval (Off to 3h, default 15s).
• Layout — the Single column toggle switches the panel grid to one full-width panel per row.

CPU

Three tabs:

• Usage — Total, User, System, IOWait, and Steal, as percentages of the server’s whole CPU capacity: 100% means every core is busy. (Container CPU works differently — see Docker container monitoring.)
• Load — 1m Load, 5m Load, 15m Load load averages.
• Temp — one line per temperature sensor the collector can read; virtual machines usually expose none.

Memory

One chart with Used, Cached, Buffered, and Swap lines. Cached and buffered memory is reclaimable, so a high cached value is normal on a busy server — watch Used and Swap for pressure.

Disk

Four tabs:

• Usage — how full the filesystem is over time.
• I/O — read and write throughput.
• IOPS — read and write operations per second.
• Busy % — the share of time the device spent servicing requests.

I/O, IOPS, and Busy % break down by physical device (nvme0n1, sda, …) with the Per-device toggle, and the stats grid splits into Read and Write columns — including a Total row for data moved over the visible range.

Network

Four tabs — Throughput (In/Out), Packets, Errors, and Connections (TCP connections by state, such as Established and LISTEN). Throughput’s stats grid splits into ↓/↑ columns and adds a Total row: data transferred over the visible range. A summary card beside the panels shows the current ↓/↑ rates and the interface count.

When a panel is missing

Panels reflect what the collector finds on the server: without reachable Docker the Containers panel stays at “No containers detected on this server” (details), and Disk Health renders only for physical drives on bare-metal servers. A panel is missing or empty walks the checks panel by panel. If every panel is empty and the server shows Offline, that’s a delivery problem, not a display one — start with No data appearing.