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
Compose snapshot warning preservation with current backup-date repair
pulse-triage[bot]9b607668b95b
diff --cc docs/release-control/v6/internal/subsystems/alerts.mdindex d43854cb27,de838fdf0e..b20715e0d2--- a/docs/release-control/v6/internal/subsystems/alerts.md+++ b/docs/release-control/v6/internal/subsystems/alerts.md@@@ -15,25 -15,27 +15,44 @@@## Purpose+### Listed backups need an observed success date to resolve age warnings++The backup-age evaluator retains an existing subject's occurrence, severity,+acknowledgement and last trusted evidence when its still-listed rollup has no+success date, a zero date or a future date. Such a date supplies neither a new+age nor recovery. For multiple provider rollups of one subject, the newest+usable success date wins regardless of input order; an unobserved date cannot+hide an older valid breach or displace a valid recent recovery. A fresh valid+date still recovers normally. Explicit policy exclusions, disabled rules and+removal from the supplied complete inventory keep their existing semantics.++`TestCheckBackupsRequiresObservedSuccessDates` exercises the real manager with+PVE/PBS linked guests, PBS orphans and PMG subjects, occurrence/event retention,+provider ordering, same-VMID cross-instance isolation and policy/removal controls.+Its opt-in browser frames come from `CheckBackups` and `GetActiveAlerts`.+This is age-evidence handling only: no change to backup execution, source+inventory readiness, snapshot alerts, native freeze/thaw safety or notification+delivery, and no proof of a reported installation's recovery.+ ### A listed snapshot with an unknown creation date is not recovered++ Snapshot warning cleanup distinguishes an absent snapshot from a still-listed+ snapshot whose creation time is missing, non-positive Unix time or in the future.+ After current guest policy and overrides are applied, an unknown date retains+ only that snapshot's existing canonical occurrence, including its trusted+ age/size evidence, acknowledgement and observation time. It neither creates a+ new occurrence nor refreshes old evidence. A trustworthy dated observation,+ authoritative removal, exclusion or disablement still follows normal recovery.+ The global alerting switch remains an evaluation pause, not evidence of recovery.++ This is deliberately conservative for both age and size warnings: an incomplete+ snapshot observation does not independently update either metric. It introduces+ no guest, snapshot, backup, filesystem or freeze/thaw operation.+ `snapshot_date_observation_test.go` checks repeated gaps, epoch conversion,+ exact occurrence/evidence preservation, lifecycle events, independent instances,+ policy changes, trustworthy recovery and removal. The real manager's exported+ frames feed the production Alerts API adapter and Overview/card browser fixture+ at desktop and narrow viewports; this is not installed guest recovery.-### Legacy alert-history compaction releases removed-row storageExpiry, duplicate-occurrence compaction and ID removal allocate backing storage