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
Preserve backup completion and agent startup contracts together
pulse-triage[bot]806b9ac5168c
diff --cc docs/release-control/v6/internal/subsystems/frontend-primitives.mdindex 6da432bdc2,27753f069d..76c5f97463--- a/docs/release-control/v6/internal/subsystems/frontend-primitives.md+++ b/docs/release-control/v6/internal/subsystems/frontend-primitives.md@@@ -20,22 -20,18 +20,34 @@@## Purpose+### Agent first-report status++Machines, resource detail drawers and agent connection rows use the shared+"Waiting for first report" label for monitoring's bounded pending startup+state. Machines treats that informational state as unknown rather than an outage.+The collapsed machine row shows the wording beside its name and suppresses+cached metric bars until accepted telemetry arrives. Consumers must not infer+the wait from a browser timer or hide a provider failure behind it. The expanded+drawer presents the wait as information and does not synthesize a current+chart reading from absent or cached metrics. Stored history remains available.+The shared history query immediately withdraws cached live replies and current+fallbacks when the owning source loses reporting authority. That transition+starts a fresh read without waiting for the poll, while retaining actual stored+series and rejecting a late live reply from the previous reporting state.+Pending API polls retain their own wording.++ ### Backups distinguishes completed points from inventory entries (24 October 2026)++ The existing health strip names completed restore points and separately counts+ running and failed entries. The existing per-day chart measures only completed+ restore points in both count and volume modes, while the dated table and its+ filters keep incomplete entries available for inspection. Table and day-group+ counters name entries so they cannot imply completion. The incomplete-only+ chart state says that no completed dated points are visible, not that no+ backup activity occurred. The consuming Backups tests cover summary, chart,+ volume, date selection and route views together; existing table interaction+ primitives, access boundaries and routes are unchanged.+### Backup posture failure and retry stay source-local (24 October 2026)The Backups posture notice offers a keyboard-operable retry with the existingdiff --cc docs/release-control/v6/internal/subsystems/storage-recovery.mdindex 3b69ac0de6,c188a1a802..c4b457fcd4--- a/docs/release-control/v6/internal/subsystems/storage-recovery.md+++ b/docs/release-control/v6/internal/subsystems/storage-recovery.md@@@ -21,15 -21,20 +21,29 @@@## Purpose+### Agent startup is not storage evidence++An agent's pending first report after a server restart is a monitoring-owned+delivery state. Its retained enrollment and historical receipt carry no fresh+storage metrics, healthy storage verdict or recovery evidence. Expiry of that+reporting lease likewise supplies no new zero-valued chart observation or+recovery proof. Storage and+recovery consumers continue to require their own source observations.++ ### Completed restore totals exclude incomplete inventory (24 October 2026)++ The Backups restore-point total, completed-byte total, PBS-target count and+ per-day count/volume chart all exclude explicitly running or terminally+ incomplete artifacts. The same completion predicate selects the last backup.+ Running and failed entries remain in the dated inventory and row evidence,+ with separate summary counts; inventory and day-group counts name entries,+ not completed backups. Unknown dates and unverified completed points remain+ evidence, not absent or failed points. Completion establishes neither an+ independent backup (guest snapshots remain distinct), tested restore nor guest+ thaw. Registered recovery-model and consuming-table tests cover mixed,+ incomplete-only, unknown-date and completion-transition controls without any+ new backup execution, QGA requests, schema or persisted state.+### Failed posture refreshes withdraw retained assessments (24 October 2026)Protection posture remains visible while a refresh is pending, but a settled