Mockup · sample data · nothing is connected
live

Overview

Every host reporting in, with the things that actually break at the top. Agents dial out to the panel, so nothing here required opening a port at the house.

Updates

Nothing is ever applied automatically. Choose packages individually, take security-only, or approve a whole host — then confirm with your authenticator.

0 selected across 0 hosts

Storage

Every drive in the rack, health first. SMART attributes predict a failure; a capacity bar does not. Projection is from the fill rate over the last 30 days.

DriveHostModelTempHours HealthUsedFreeFull in
Game server drives read for SMART. Its controller is still in IDE mode, which hides most attributes. Switching to AHCI is already on the rack build order; until then the agent reports capacity but not health.

Power

All four units over NUT. Two are in the office; the bedroom and kitchen units carry the WAN path, so they matter to the rack even though they are nowhere near it.

NUT path health is checked separately from battery state. The cloud server has no UPS of its own to talk to — it subscribes over the network, and its link runs through switches on the other unit. A broken path is invisible until an outage, which is exactly when finding out is most expensive.

Services & backups

A host at 4% CPU with Jellyfin returning 502 is down in every sense that matters. Backup freshness is here too — the characteristic failure is a job that quietly stopped weeks ago.

CheckHostKindLatencyStateLast OK

Backups

TargetRepoSnapshotsSizeFreshnessLast run

Environment

Rack ambient from the Govee H5075 over BlueZ, relayed by the media server agent. Draw from the Govee smart plug — the first real wattage numbers, replacing the estimates the build sheet has been reasoning with.

Both sensors were already budgeted in the rack build and had nowhere to report to. Measured draw is what tells you whether the UPS runtime estimates were right — the build sheet assumed ~475 W across the media and cloud servers.