Skip to content

armgit / Pulse

Public Imported from GitHub
0

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.

Keep connection liveness separate from backup freshness

pulse-triage[bot]da747553d9ad
diff --git a/docs/UNIFIED_AGENT.md b/docs/UNIFIED_AGENT.md
index 0b891d5ead..e5b698559e 100644
--- a/docs/UNIFIED_AGENT.md
+++ b/docs/UNIFIED_AGENT.md
@@ -1181,9 +1181,10 @@ API collection is current. Guest-agent disk readings are not backup inventory.
seen through PVE are distinct sources; see [PBS data sources](PBS.md#data-source-indicator)
and [Recovery](RECOVERY.md#missing-or-inconsistent-evidence).
3. **Inspect ordinary collection, not a new probe.** In **Settings →
- Infrastructure**, check the affected PVE connection's existing status and
- last successful collection, together with the original redacted error and
- time. The server checks online nodes and queryable storage configured for
+ Infrastructure**, check the affected saved PVE connection and existing
+ status. Keep connection/agent liveness separate from backup collection
+ freshness; use existing collection timestamps where available, and retain
+ the original redacted error and time. The server checks online nodes and queryable storage configured for
backup content. A failed, unavailable or partial read is not an empty
inventory; a successful connection test is not proof of sustained collection.
4. **Repair access only when the evidence supports it.** Ask the Proxmox
diff --git a/frontend-modern/public/docs/UNIFIED_AGENT.md b/frontend-modern/public/docs/UNIFIED_AGENT.md
index 0b891d5ead..e5b698559e 100644
--- a/frontend-modern/public/docs/UNIFIED_AGENT.md
+++ b/frontend-modern/public/docs/UNIFIED_AGENT.md
@@ -1181,9 +1181,10 @@ API collection is current. Guest-agent disk readings are not backup inventory.
seen through PVE are distinct sources; see [PBS data sources](PBS.md#data-source-indicator)
and [Recovery](RECOVERY.md#missing-or-inconsistent-evidence).
3. **Inspect ordinary collection, not a new probe.** In **Settings →
- Infrastructure**, check the affected PVE connection's existing status and
- last successful collection, together with the original redacted error and
- time. The server checks online nodes and queryable storage configured for
+ Infrastructure**, check the affected saved PVE connection and existing
+ status. Keep connection/agent liveness separate from backup collection
+ freshness; use existing collection timestamps where available, and retain
+ the original redacted error and time. The server checks online nodes and queryable storage configured for
backup content. A failed, unavailable or partial read is not an empty
inventory; a successful connection test is not proof of sustained collection.
4. **Repair access only when the evidence supports it.** Ask the Proxmox
diff --git a/scripts/tests/test_pve_backup_troubleshooting_docs.py b/scripts/tests/test_pve_backup_troubleshooting_docs.py
index 44215d7f0a..b871737f8f 100644
--- a/scripts/tests/test_pve_backup_troubleshooting_docs.py
+++ b/scripts/tests/test_pve_backup_troubleshooting_docs.py
@@ -66,6 +66,8 @@ class PVEBackupTroubleshootingDocsTest(unittest.TestCase):
for phrase in ("node, storage, guest type/ID and time", "Proxmox → Backups → By date",
"Coverage posture is a different reading", "distinct sources",
"failed, unavailable or partial read is not an empty inventory",
+ "Keep connection/agent liveness separate from backup collection freshness",
+ "existing collection timestamps where available",
"OK task does not prove guest thaw", "Do not run another backup or restore",
"outside backups", "without manual guest-agent probes",
"Keep token secrets, full ACL listings and private infrastructure details"):