Files
Ryan Yin 9b68cfdb8a feat(backup): alert when the last successful backup goes stale
The backup unit publishes `restic_backup_last_success_timestamp_seconds` for the node_exporter textfile collector, and a rejected alert now fails the notify unit instead of exiting 0.

Assisted-by: DeepSeek Harness 0.2.1-rc.2 (deepseek-flash)
2026-10-22 00:54:27 +08:00

1.1 KiB

Monitoring & Alerting

Alert Rules & Recording Rules

Backup Freshness

modules/nixos/base/restic-backup.nix writes restic_backup_last_success_timestamp_seconds to node_exporter's textfile collector after a successful run. alert_rules/restic-backup.yml alerts when it is older than two days (the schedule is daily) or absent entirely.

TODO

  • Dead-man switch: Watchdog in alert_rules/general.yml always fires (vector(1)) but is routed to the null receiver in alert.nix, so a dead alerting pipeline looks identical to a healthy one. Route it to an external heartbeat service (healthchecks.io, Uptime Kuma, PagerDuty DeadMansSnitch) that notifies when the heartbeat stops, or run an out-of-band probe against Alertmanager.