Proxmox Notifications: Setting Up Alerts for Backups, Replication, and Node Health Before Something Breaks Silently

Every other article on this site that mentions a scheduled Proxmox job, backups, replication, HA, eventually says some version of “check the GUI periodically to make sure it’s still running.” That’s fine advice until the day you stop checking, which is also usually the day it matters most. Proxmox has had a real, built-in notification system since 8.1 that can push a failed backup, a broken replication job, or a flapping node straight to email, a webhook, Slack, Discord, or whatever else you already watch, and most homelabs never turn it on past whatever came configured by default. This is the setup that closes that gap. ...

November 2, 2026 · 7 min

SMART Monitoring and Drive Health Alerts: Catching a Dying Drive Before It Takes Data With It

Burn-in testing catches a bad drive before it ever holds data. Bit rot scrubbing catches silent corruption on drives that are otherwise working fine. Neither one watches a healthy drive for the slow, specific warning signs that show up months or years into its working life, the gradually climbing error counts that mean a drive is dying, not corrupted or defective out of the box. That’s a separate job: ongoing SMART monitoring with an actual alert attached to it, not a dashboard you remember to check every few months. ...

October 7, 2026 · 7 min

Self-Hosted Monitoring: Setting Up Uptime Kuma and Grafana So You Know Before Your Users Do

The first time most people find out a self-hosted service is down is when someone tries to use it and it isn’t there. That’s the wrong order. If you’re running more than two or three services at home - Immich, a media server, a reverse proxy, whatever - you’ve already got enough surface area for something to quietly die on a Tuesday and stay dead until you notice by accident. ...

August 20, 2026 · 7 min