container.<name>.down: should be up and isn't — not merely stopped; the default alert watches that

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-19 15:10:17 -07:00
parent cb1617c2b8
commit 08fb9d6e38
3 changed files with 54 additions and 3 deletions
@@ -136,6 +136,9 @@ services.failed|failed_names|running            every 30 s
 service.<unit>.active|state                     one pair per service that is enabled, up or failed
 containers.total|running|unhealthy              every 15 s (Docker or Podman, if present)
 container.<name>.running|state|health|mem|cpu   mem and cpu read from the container's cgroup
+container.<name>.down                           should be up and isn't: Docker couldn't start it, it is
+                                                stuck restarting, or it died non-zero with no policy to
+                                                restart it — *not* a container someone stopped
 updates.pending|security|reboot_required        every 5 min
 zfs.<pool>.health|healthy|size|used|used_pct|frag   every 1 min
 smart.<dev>.passed|warnings|power_on|wear       every 10 min, never waking a sleeping disk