Critical systemd Units Need Their Own Health Signal
Container monitoring does not cover host services such as Docker, networking, tunnels, backup timers or other systemd-managed dependencies.
Container monitoring does not cover host services such as Docker, networking, tunnels, backup timers or other systemd-managed dependencies.
A service can fail to start, start and exit, run as the wrong user, or wait on a dependency.
Service state, bind failures and restart loops often explained a broken PBX before I needed to inspect a single SIP packet.
A systemd timer can fire on schedule while the backup service itself fails, times out or exits before producing a valid set.
A runaway process can exhaust memory, spawn too many tasks, or consume CPU until unrelated services become unhealthy.
A red backup alert identifies the outcome but usually does not explain which command, mount or permission caused the failure.
Stopping only the shell does not necessarily stop pg_dump, tar or helper processes that the shell launched.
A backup that hangs forever can block future runs and create false confidence without ever producing a usable recovery point.