A panel is missing or empty

A server’s page shows panels for what its collector actually finds — a server with no Docker, no physical drives, or no failed services has less to show, and that’s not an error. The checks below assume the server is Online and its CPU and memory charts are drawing; if everything is empty, the problem is delivery, not display — start with No data appearing instead.

The Containers panel says “No containers detected on this server.”

The panel is always on the page; this text is what an empty probe leaves behind. Two situations produce it:

• The server doesn’t run Docker. Nothing to fix — the panel fills on its own if Docker arrives later, provided the collector can reach it (next point).
• Docker is running containers, but the collector can’t see them. Almost always Docker was installed after the collector, so the collector’s user never joined the docker group. The two-line fix (or a re-run of the install command) is in Docker container monitoring.

There is no Disk Health panel

On virtual servers — VPS, VM, LXC — this is by design, and it’s an absence, not an empty state: virtualized disks expose no SMART data, so the panel doesn’t render at all. Disk health (SMART) explains the limit.

On a bare-metal server with physical drives, a missing Disk Health panel usually means the install predates the drives (or the collector was never granted disk capabilities — check the Permission Limitations card). Re-run the install command: it re-probes the hardware, grants what the drives need, and the panel appears within a few minutes of the service restarting.

A service is missing from the Services panel

The 5-minute snapshot covers .service units that are active, changing state, or failed — a unit that is stopped and supposed to be stopped isn’t listed, by design. If the unit is genuinely running and still absent, remember the panel’s snapshot cadence: a just-started unit can take one 5-minute cycle to show. Which units appear has the selection rules.

The CPU panel’s Temp tab shows no sensors

The collector charts every temperature sensor it can read. Virtual servers usually expose none, so an empty Temp tab on a VM has nothing to fix — see the CPU panel notes.

Check the Permission Limitations card

Whatever the missing panel, scroll to the bottom of the server’s page. If the collector skipped a feature for lack of privileges, the Permission Limitations card is there and names each one — on our demo server it reads “zfs status requires root”. No card at all means nothing was skipped.

If the card names something the install script can grant — disk (SMART) capabilities or Docker socket access — re-run the install command; it re-probes the server and grants what the hardware calls for. What the card can and can’t report is covered in Requirements & permissions.

Still stuck

Grab the last few minutes of collector logs:

journalctl -u monitorable-collector --since "-10m" --no-pager

A healthy collector logging no errors while a panel stays empty means the server genuinely has nothing to report for it. If the logs show delivery errors instead, switch to No data appearing — the named error sections there cover each one.