Guide
What the catalog offers for watching a home server today, what each of these services actually sees, and the blind spot none of them can cover on their own.
Monitoring is one of the thinner corners of this catalog today, and it is better to say so than to pad the page: one recipe here exists to watch things, and the other two are useful sources of signal that people already run. Adding a metrics stack — collection, storage and dashboards — is a task on the roadmap rather than something the catalog can hand you now.
What you can build today is still worth building. Checks against the services you care about, a notification that reaches you rather than a dashboard you would have to remember to open, and a status page so the household stops asking. Set the check interval where a failure is noticed in minutes and a flapping service does not wake you at four in the morning.
The blind spot is structural: a monitor that runs on the machine it watches cannot report that machine’s death. Nothing in this set fixes that from the inside. The cheap answer is a second, small device — a Raspberry Pi in the same house, or a small VPS elsewhere — running one more copy of the monitor with a single check pointed back at the server. Two machines that watch each other cover almost everything a home setup will ever hit.
Sets
The sum of the minimums the recipes below declare. It is a floor, not a recommendation: leave room for the operating system, backups and growth.
Why it is here: The dedicated monitor in the catalog: HTTP, TCP, ping and certificate checks on a schedule, notifications to the channel you already read, and a status page for the people who ask you whether something is down. It is also the only recipe here whose entire job is this.
Why it is here: Not a monitor, but the closest thing to visibility into what the network is doing: which device asked for what, how often, and what was blocked. A resolver log answers questions an uptime check cannot.
Why it is here: Worth listing because it is already collecting history in many houses — temperature, power draw, whether a machine responds. It turns a home server into something with sensors rather than only endpoints.