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
Align backup inspection help with provider evidence labels
pulse-triage[bot]e85886d3a1d8
diff --git a/docs/PBS.md b/docs/PBS.mdindex 79a26c8dbc..20eee9dc00 100644--- a/docs/PBS.md+++ b/docs/PBS.md@@ -403,8 +403,11 @@ backup or working protection from the strip alone.Check one affected guest without changing its setup:1. Open **Proxmox → Backups → Coverage** and expand that guest. Read its- protection explanation and the PBS **Job**, **History** and **Access**- evidence. Access describes permissions; if provider evidence is absent,+ protection explanation and the PBS **Source**, **Reported outcome**,+ **History** and **Access** evidence. Source distinguishes backup inventories+ from retained points. A successful inventory read is not a successful backup+ job; the outcome can also include retained-point evidence. Access describes+ permissions; if provider evidence is absent,record that rather than interpreting it as healthy. These are backupevidence states, not the PBS host's CPU/metrics History chart.2. Compare the listed backup with the existing record in PBS: server,@@ -417,7 +420,7 @@ Check one affected guest without changing its setup:timestamp. A **guest snapshot** is not a PBS backup. Check the existingbackup task and verification result for that same point in PBS.3. If the records still disagree, report the Pulse version, one guest's- protection explanation, PBS Job/History/Access values and the matching+ protection explanation, PBS Source/Reported outcome/History/Access values and the matchingpoint's Created time, State and PBS verification result. Use consistentplaceholders for private server, datastore, namespace and guest identities.Do not share tokens, full API responses, HAR exports, or screenshots with secrets.@@ -431,8 +434,9 @@ its explanation and Provider evidence. A **Kept** point has no reportedverification result. **Prune protection** is shown separately in the By datedetail and never replaces a reported **Verified** or **Unverified** state.Older Pulse versions may show **Protected** for the prune flag instead. That-point label alone does not establish verification. **Job OK** is not an-individual point's verification result. Use the records already available,+point label alone does not establish verification. **Reported outcome: Success**+can describe an inventory read, not a backup job or an individual point's+verification result. Use the records already available,without running Diagnostics or another verification just to compare them.Do not delete backups, clear History, change retention or freshness settings,diff --git a/docs/RECOVERY.md b/docs/RECOVERY.mdindex df294431e8..368b8473ad 100644--- a/docs/RECOVERY.md+++ b/docs/RECOVERY.md@@ -382,8 +382,10 @@ protected. Compare one existing archive with the same workload in Pulse:local storage: a PBS-backed storage target can also appear as a PVE file.3. Open **Coverage**, clear its posture filter and expand that same workload.Read the posture explanation and **Provider evidence**: provider,- **Scope**, **Job**, **History** and **Access**. Keep **All backup locations**- for a whole-workload comparison. Selecting a location limits the listed+ **Scope**, **Source**, **Reported outcome**, **History** and **Access**.+ A successful inventory read is not a backup-job completion result; keep task+ and restore-point states separate. Keep **All backup locations** for a+ whole-workload comparison. Selecting a location limits the listedartifacts and backup age, but does not recalculate the workload's posture.A visible archive and a green connection do not establish that the postureassessment received the same complete, correctly linked evidence. Read thediff --git a/docs/release-control/v6/internal/subsystems/storage-recovery.md b/docs/release-control/v6/internal/subsystems/storage-recovery.mdindex ee448d2537..cfbe042c58 100644--- a/docs/release-control/v6/internal/subsystems/storage-recovery.md+++ b/docs/release-control/v6/internal/subsystems/storage-recovery.md@@ -30,7 +30,10 @@ The rollup's `jobState` is displayed as Reported outcome, never Job or Collectioan inventory observation can supply it, but a newer retained point can alsosupply the outcome beside an older observation's source. Visible wrapping copykeeps this evidence distinct from actual task and restore-point states. History,-access, reported values, protection, dates and policy do not change.+access, reported values, protection, dates and policy do not change. The shipped+PBS/PVE comparison guides name the same Source/Reported outcome fields and+keep successful inventory reads separate from backup-task completion. Rendered+help tests preserve this distinction and every original-recovery safety limit.Normal-suite `ProxmoxCoverageTable.test.tsx` covers known/unknown/literal sources,all reported outcomes and narrow/wide rendering. `ProxmoxBackupsTable.test.tsx`diff --git a/docs/release-control/v6/internal/subsystems/unified-resources.md b/docs/release-control/v6/internal/subsystems/unified-resources.mdindex f072c8a183..d34cdb0c36 100644--- a/docs/release-control/v6/internal/subsystems/unified-resources.md+++ b/docs/release-control/v6/internal/subsystems/unified-resources.md@@ -32,7 +32,10 @@ The rollup's `jobState` is displayed as Reported outcome, never Job or Collectioan inventory observation can supply it, but a newer retained point can alsosupply the outcome beside an older observation's source. Visible wrapping copykeeps this evidence distinct from actual task and restore-point states. History,-access, reported values, protection, dates and policy do not change.+access, reported values, protection, dates and policy do not change. The shipped+PBS/PVE comparison guides name the same Source/Reported outcome fields and+keep successful inventory reads separate from backup-task completion. Rendered+help tests preserve this distinction and every original-recovery safety limit.Normal-suite `ProxmoxCoverageTable.test.tsx` covers known/unknown/literal sources,all reported outcomes and narrow/wide rendering. `ProxmoxBackupsTable.test.tsx`diff --git a/frontend-modern/public/docs/PBS.md b/frontend-modern/public/docs/PBS.mdindex 79a26c8dbc..20eee9dc00 100644--- a/frontend-modern/public/docs/PBS.md+++ b/frontend-modern/public/docs/PBS.md@@ -403,8 +403,11 @@ backup or working protection from the strip alone.Check one affected guest without changing its setup:1. Open **Proxmox → Backups → Coverage** and expand that guest. Read its- protection explanation and the PBS **Job**, **History** and **Access**- evidence. Access describes permissions; if provider evidence is absent,+ protection explanation and the PBS **Source**, **Reported outcome**,+ **History** and **Access** evidence. Source distinguishes backup inventories+ from retained points. A successful inventory read is not a successful backup+ job; the outcome can also include retained-point evidence. Access describes+ permissions; if provider evidence is absent,record that rather than interpreting it as healthy. These are backupevidence states, not the PBS host's CPU/metrics History chart.2. Compare the listed backup with the existing record in PBS: server,@@ -417,7 +420,7 @@ Check one affected guest without changing its setup:timestamp. A **guest snapshot** is not a PBS backup. Check the existingbackup task and verification result for that same point in PBS.3. If the records still disagree, report the Pulse version, one guest's- protection explanation, PBS Job/History/Access values and the matching+ protection explanation, PBS Source/Reported outcome/History/Access values and the matchingpoint's Created time, State and PBS verification result. Use consistentplaceholders for private server, datastore, namespace and guest identities.Do not share tokens, full API responses, HAR exports, or screenshots with secrets.@@ -431,8 +434,9 @@ its explanation and Provider evidence. A **Kept** point has no reportedverification result. **Prune protection** is shown separately in the By datedetail and never replaces a reported **Verified** or **Unverified** state.Older Pulse versions may show **Protected** for the prune flag instead. That-point label alone does not establish verification. **Job OK** is not an-individual point's verification result. Use the records already available,+point label alone does not establish verification. **Reported outcome: Success**+can describe an inventory read, not a backup job or an individual point's+verification result. Use the records already available,without running Diagnostics or another verification just to compare them.Do not delete backups, clear History, change retention or freshness settings,diff --git a/frontend-modern/public/docs/RECOVERY.md b/frontend-modern/public/docs/RECOVERY.mdindex df294431e8..368b8473ad 100644--- a/frontend-modern/public/docs/RECOVERY.md+++ b/frontend-modern/public/docs/RECOVERY.md@@ -382,8 +382,10 @@ protected. Compare one existing archive with the same workload in Pulse:local storage: a PBS-backed storage target can also appear as a PVE file.3. Open **Coverage**, clear its posture filter and expand that same workload.Read the posture explanation and **Provider evidence**: provider,- **Scope**, **Job**, **History** and **Access**. Keep **All backup locations**- for a whole-workload comparison. Selecting a location limits the listed+ **Scope**, **Source**, **Reported outcome**, **History** and **Access**.+ A successful inventory read is not a backup-job completion result; keep task+ and restore-point states separate. Keep **All backup locations** for a+ whole-workload comparison. Selecting a location limits the listedartifacts and backup age, but does not recalculate the workload's posture.A visible archive and a green connection do not establish that the postureassessment received the same complete, correctly linked evidence. Read thediff --git a/frontend-modern/src/features/docs/__tests__/pveCoverageGuide.test.ts b/frontend-modern/src/features/docs/__tests__/pveCoverageGuide.test.tsindex 2502e6b779..ca93ec5000 100644--- a/frontend-modern/src/features/docs/__tests__/pveCoverageGuide.test.ts+++ b/frontend-modern/src/features/docs/__tests__/pveCoverageGuide.test.ts@@ -43,6 +43,9 @@ describe('local PVE Coverage comparison guidance', () => {const latest = COVERAGE_COLUMNS.find((column) => column.id === 'latest')!;expect(text).toContain(latest.label);for (const distinction of [+ 'Scope, Source, Reported outcome, History and Access',+ 'A successful inventory read is not a backup-job completion result',+ 'keep task and restore-point states separate','not the protection policy',"does not refresh collection or change a backup's age","does not recalculate the workload's posture",diff --git a/frontend-modern/src/utils/__tests__/pbsProtectionHelp.test.ts b/frontend-modern/src/utils/__tests__/pbsProtectionHelp.test.tsindex d88e424be6..2dc90404c3 100644--- a/frontend-modern/src/utils/__tests__/pbsProtectionHelp.test.ts+++ b/frontend-modern/src/utils/__tests__/pbsProtectionHelp.test.ts@@ -45,7 +45,9 @@ describe('PBS protection disagreement help', () => {);expect(steps).toHaveLength(3);expect(steps[0]).toContain('Proxmox → Backups → Coverage');- expect(steps[0]).toContain('Job, History and Access');+ expect(steps[0]).toContain('Source, Reported outcome, History and Access');+ expect(steps[0]).toContain('A successful inventory read is not a successful backup job');+ expect(steps[0]).toContain('the outcome can also include retained-point evidence');expect(steps[0]).toContain('provider evidence is absent');expect(steps[0]).toContain('not the PBS host');expect(steps[1]).toContain(@@ -60,10 +62,8 @@ describe('PBS protection disagreement help', () => {expect(steps[1]).toContain('guest snapshot is not a PBS backup');expect(steps[2]).toContain('protection explanation');expect(article().querySelector('pre')).toBeNull();- const coverage = read('frontend-modern/src/features/proxmox/ProxmoxCoverageTable.tsx');- expect(coverage).toContain('Job {evidenceQualityLabel(provider.jobState)}');- expect(coverage).toContain('History {evidenceQualityLabel(provider.historyCompleteness)}');- expect(coverage).toContain('Access {evidenceQualityLabel(provider.permissions)}');+ // Runtime consumer tests own its rendered labels. Keep this check on the+ // rendered guide's meaning, not a source-code spelling or Markdown wrap.});it('distinguishes the available observations without claiming a PBS cause or verification failure', () => {@@ -76,7 +76,9 @@ describe('PBS protection disagreement help', () => {'Verified with a workload still needing attention is a separate assessment disagreement',);expect(text()).toContain('retain its explanation and Provider evidence');- expect(text()).toContain("Job OK is not an individual point's verification result");+ expect(text()).toContain(+ "Reported outcome: Success can describe an inventory read, not a backup job or an individual point's verification result",+ );expect(text()).toContain('without running Diagnostics or another verification');});@@ -151,6 +153,8 @@ describe('PBS protection disagreement help', () => {expect(text()).toContain('Do not share tokens, full API responses, HAR exports, or screenshots with secrets',);- expect(text()).toContain("one guest's protection explanation, PBS Job/History/Access values");+ expect(text()).toContain(+ "one guest's protection explanation, PBS Source/Reported outcome/History/Access values",+ );});});