Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.
Go aialertsdashboarddockerdocker-monitoringgohomelabinfrastructure-monitoringkubernetesmonitoringmspproxmoxproxmox-backup-serverproxmox-mail-gatewayproxmox-veself-hostedtruenastypescriptvspherewebhooks
Keep Docker maintenance guidance faithful to shared host identity
pulse-triage[bot]83f04d76b83f
diff --git a/docs/DOCKER.md b/docs/DOCKER.mdindex 12a9e33a92..a8832a4a48 100644--- a/docs/DOCKER.md+++ b/docs/DOCKER.md@@ -145,9 +145,9 @@ is worth reporting, even when memory no longer grows.## Runtime and container alert scopes-In **Alerts → Thresholds → Docker**, a container runtime (Docker or Podman),-its containers and the machine running it are different alert resources.-Turning off one check is not a blanket mute for everything on that machine.+In **Alerts → Thresholds → Docker**, runtime connectivity, per-container alert+rules and machine maintenance have different scopes. Turning off one check+is not a blanket mute for everything on that machine.- **Runtime Offline Alerts** controls that runtime's connectivity alert. Itdoes **not** turn off alerts for its containers. The runtime row's general@@ -159,9 +159,11 @@ Turning off one check is not a blanket mute for everything on that machine.check the saved row. Other containers and the machine keep their own rules.Turning off only the container's **Offline Alerts** leaves its other checksenabled. Neither setting stops collection or hides readings.-- **Machine maintenance** has a different scope. A window covering the machine- and its descendants also suppresses wanted machine alerts, not just Docker- alerts. It is not equivalent to muting one runtime and its containers while+- **Machine maintenance** has a different scope. On a unified-agent host, the+ runtime's **Manage** controls apply to the machine too. A window covering+ the machine and its descendants also suppresses wanted machine alerts, not+ just Docker alerts. It is not equivalent to muting one runtime and its+ containers whilekeeping the machine monitored. Global or platform-wide Off controls alsoaffect more than one runtime; do not use them for that narrower job.diff --git a/frontend-modern/public/docs/DOCKER.md b/frontend-modern/public/docs/DOCKER.mdindex 12a9e33a92..a8832a4a48 100644--- a/frontend-modern/public/docs/DOCKER.md+++ b/frontend-modern/public/docs/DOCKER.md@@ -145,9 +145,9 @@ is worth reporting, even when memory no longer grows.## Runtime and container alert scopes-In **Alerts → Thresholds → Docker**, a container runtime (Docker or Podman),-its containers and the machine running it are different alert resources.-Turning off one check is not a blanket mute for everything on that machine.+In **Alerts → Thresholds → Docker**, runtime connectivity, per-container alert+rules and machine maintenance have different scopes. Turning off one check+is not a blanket mute for everything on that machine.- **Runtime Offline Alerts** controls that runtime's connectivity alert. Itdoes **not** turn off alerts for its containers. The runtime row's general@@ -159,9 +159,11 @@ Turning off one check is not a blanket mute for everything on that machine.check the saved row. Other containers and the machine keep their own rules.Turning off only the container's **Offline Alerts** leaves its other checksenabled. Neither setting stops collection or hides readings.-- **Machine maintenance** has a different scope. A window covering the machine- and its descendants also suppresses wanted machine alerts, not just Docker- alerts. It is not equivalent to muting one runtime and its containers while+- **Machine maintenance** has a different scope. On a unified-agent host, the+ runtime's **Manage** controls apply to the machine too. A window covering+ the machine and its descendants also suppresses wanted machine alerts, not+ just Docker alerts. It is not equivalent to muting one runtime and its+ containers whilekeeping the machine monitored. Global or platform-wide Off controls alsoaffect more than one runtime; do not use them for that narrower job.