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 slow PBS loading advice source-specific and non-destructive

pulse-triage[bot]021fd2791dff
diff --git a/.github/workflows/public-docs.yml b/.github/workflows/public-docs.yml
index c7a38e55fe..9ec85c87aa 100644
--- a/.github/workflows/public-docs.yml
+++ b/.github/workflows/public-docs.yml
@@ -14,6 +14,7 @@ on:
- "scripts/tests/test_public_docs_workflow.py"
- "scripts/tests/test_production_rollout_docs.py"
- "scripts/tests/test_pmg_docs.py"
+ - "scripts/tests/test_pbs_docs.py"
- "scripts/tests/test_pve_backup_troubleshooting_docs.py"
- "scripts/tests/test_vm_disk_diagnostics.py"
- "scripts/tests/test_memory_troubleshooting_docs.py"
@@ -36,6 +37,7 @@ on:
- "scripts/tests/test_public_docs_workflow.py"
- "scripts/tests/test_production_rollout_docs.py"
- "scripts/tests/test_pmg_docs.py"
+ - "scripts/tests/test_pbs_docs.py"
- "scripts/tests/test_pve_backup_troubleshooting_docs.py"
- "scripts/tests/test_vm_disk_diagnostics.py"
- "scripts/tests/test_memory_troubleshooting_docs.py"
@@ -81,6 +83,7 @@ jobs:
scripts/tests/run.sh \
test_production_rollout_docs.py \
test_pmg_docs.py \
+ test_pbs_docs.py \
test_pve_backup_troubleshooting_docs.py \
test_vm_disk_diagnostics.py \
test_memory_troubleshooting_docs.py \
diff --git a/docs/PBS.md b/docs/PBS.md
index d188c13f5f..bbfa9ebec1 100644
--- a/docs/PBS.md
+++ b/docs/PBS.md
@@ -410,10 +410,41 @@ separate symptom is missing filesystem information in a PVE VM row.
### Slow Backup Loading
-If you notice slow loading for PBS storage accessed via PVE:
-- This often happens with encrypted PBS datastores
-- The fix is to add PBS directly (this guide)
-- Direct PBS connections bypass the slow PVE content listing
+A slow backup list does not establish an encrypted-datastore or PVE-proxy
+cause. First distinguish the affected reading, without changing the setup:
+
+- **Slow Proxmox → Backups list:** note the source indicator on an existing
+ affected row. **PBS via PVE** means passthrough; **PBS** means a direct
+ connection already supplies that observation. A loaded row does not prove
+ that every backup, job or History reading is current.
+- **“Backup-age alerts were not evaluated” warning:** this is a failed monitoring
+ check, not evidence that a backup failed. Follow the
+ [evaluation warning checks](TROUBLESHOOTING.md#backup-age-alerts-were-not-evaluated).
+ Adding a connection or making the list load does not establish that this
+ separate evaluation recovered.
+- **Wrong installation, overlapping guest IDs or conflicting Coverage:** use
+ the [backup health checks](#backups-are-visible-but-coverage-says-unprotected)
+ and [cross-installation identity checks](TROUBLESHOOTING.md#monitoring-is-mixed-between-proxmox-installations).
+ Keep the existing connections and records while comparing their origin.
+
+For a report, retain the Pulse version, affected view, source indicator,
+observed loading duration and relevant existing redacted error. Use consistent
+placeholders for private server, datastore, namespace and guest identities;
+do not share full responses, HAR exports or credentials. If loading makes
+Pulse unresponsive, stop and retain the observations already available, rather
+than repeatedly refreshing or running diagnostics.
+
+A direct PBS connection is an optional planned setup change when backups are
+currently available only through PVE passthrough and you need the additional
+API-backed readings described above. It bypasses PVE's proxy listing for those
+direct observations; it is **not a guaranteed performance or evaluation fix**.
+Check for an existing direct connection first and verify the owning PBS server
+before adding anything. Keep certificate verification and privilege separation
+enabled, and confirm the expected datastores and readings after normal polling.
+Do not add or recreate connections, install an agent, restart Pulse, clear
+History, change retention/polling limits, or run a backup, verification or restore
+just to diagnose slow loading. Use the existing native backup records meanwhile;
+a loaded list or an OK task is not proof of restore readiness or guest thaw.
### Duplicate Backups
diff --git a/frontend-modern/public/docs/PBS.md b/frontend-modern/public/docs/PBS.md
index d188c13f5f..bbfa9ebec1 100644
--- a/frontend-modern/public/docs/PBS.md
+++ b/frontend-modern/public/docs/PBS.md
@@ -410,10 +410,41 @@ separate symptom is missing filesystem information in a PVE VM row.
### Slow Backup Loading
-If you notice slow loading for PBS storage accessed via PVE:
-- This often happens with encrypted PBS datastores
-- The fix is to add PBS directly (this guide)
-- Direct PBS connections bypass the slow PVE content listing
+A slow backup list does not establish an encrypted-datastore or PVE-proxy
+cause. First distinguish the affected reading, without changing the setup:
+
+- **Slow Proxmox → Backups list:** note the source indicator on an existing
+ affected row. **PBS via PVE** means passthrough; **PBS** means a direct
+ connection already supplies that observation. A loaded row does not prove
+ that every backup, job or History reading is current.
+- **“Backup-age alerts were not evaluated” warning:** this is a failed monitoring
+ check, not evidence that a backup failed. Follow the
+ [evaluation warning checks](TROUBLESHOOTING.md#backup-age-alerts-were-not-evaluated).
+ Adding a connection or making the list load does not establish that this
+ separate evaluation recovered.
+- **Wrong installation, overlapping guest IDs or conflicting Coverage:** use
+ the [backup health checks](#backups-are-visible-but-coverage-says-unprotected)
+ and [cross-installation identity checks](TROUBLESHOOTING.md#monitoring-is-mixed-between-proxmox-installations).
+ Keep the existing connections and records while comparing their origin.
+
+For a report, retain the Pulse version, affected view, source indicator,
+observed loading duration and relevant existing redacted error. Use consistent
+placeholders for private server, datastore, namespace and guest identities;
+do not share full responses, HAR exports or credentials. If loading makes
+Pulse unresponsive, stop and retain the observations already available, rather
+than repeatedly refreshing or running diagnostics.
+
+A direct PBS connection is an optional planned setup change when backups are
+currently available only through PVE passthrough and you need the additional
+API-backed readings described above. It bypasses PVE's proxy listing for those
+direct observations; it is **not a guaranteed performance or evaluation fix**.
+Check for an existing direct connection first and verify the owning PBS server
+before adding anything. Keep certificate verification and privilege separation
+enabled, and confirm the expected datastores and readings after normal polling.
+Do not add or recreate connections, install an agent, restart Pulse, clear
+History, change retention/polling limits, or run a backup, verification or restore
+just to diagnose slow loading. Use the existing native backup records meanwhile;
+a loaded list or an OK task is not proof of restore readiness or guest thaw.
### Duplicate Backups
diff --git a/scripts/tests/test_pbs_docs.py b/scripts/tests/test_pbs_docs.py
index 18314ad5c7..5cfb824d9a 100644
--- a/scripts/tests/test_pbs_docs.py
+++ b/scripts/tests/test_pbs_docs.py
@@ -148,6 +148,45 @@ class PBSDocsTest(unittest.TestCase):
self.assertNotIn("completed request with `metric=cpu`", history)
self.assertIn("does\n not prove there is no data under another target", history)
+ def slow_loading_guidance(self):
+ return " ".join(DOC.read_text().split("### Slow Backup Loading\n")[1]
+ .split("\n### ")[0].split())
+
+ def test_slow_loading_distinguishes_source_and_failed_evaluation(self):
+ guidance = self.slow_loading_guidance()
+ for phrase in ("does not establish an encrypted-datastore or PVE-proxy cause",
+ "**PBS via PVE** means passthrough", "**PBS** means a direct connection already",
+ "failed monitoring check, not evidence that a backup failed",
+ "does not establish that this separate evaluation recovered"):
+ with self.subTest(phrase=phrase):
+ self.assertIn(phrase, guidance)
+ self.assertIn("TROUBLESHOOTING.md#backup-age-alerts-were-not-evaluated", guidance)
+ self.assertIn("#backups-are-visible-but-coverage-says-unprotected", guidance)
+ self.assertIn("TROUBLESHOOTING.md#monitoring-is-mixed-between-proxmox-installations", guidance)
+
+ def test_slow_loading_does_not_prescribe_a_connection_as_a_fix(self):
+ guidance = self.slow_loading_guidance()
+ self.assertIn("optional planned setup change", guidance)
+ self.assertIn("only through PVE passthrough", guidance)
+ self.assertIn("not a guaranteed performance or evaluation fix", guidance)
+ self.assertIn("Check for an existing direct connection first", guidance)
+ self.assertIn("certificate verification and privilege separation enabled", guidance)
+ self.assertNotIn("The fix is to add PBS directly", guidance)
+ self.assertIn("Do not add or recreate connections, install an agent, restart Pulse, clear History", guidance)
+ self.assertIn("change retention/polling limits", guidance)
+ self.assertIn("or run a backup, verification or restore", guidance)
+ self.assertIn("not proof of restore readiness or guest thaw", guidance)
+
+ def test_slow_loading_evidence_is_bounded_private_and_passive(self):
+ guidance = self.slow_loading_guidance()
+ self.assertIn("Pulse version, affected view, source indicator, observed loading duration", guidance)
+ self.assertIn("relevant existing redacted error", guidance)
+ self.assertIn("consistent placeholders", guidance)
+ self.assertIn("do not share full responses, HAR exports or credentials", guidance)
+ self.assertIn("stop and retain the observations already available", guidance)
+ self.assertIn("rather than repeatedly refreshing or running diagnostics", guidance)
+ self.assertIn("Use the existing native backup records meanwhile", guidance)
+
def test_every_documented_shell_recipe_parses(self):
for command in blocks():
with self.subTest(command=command):
diff --git a/scripts/tests/test_public_docs_workflow.py b/scripts/tests/test_public_docs_workflow.py
index ffdc373f2e..d6d6cfa3d8 100644
--- a/scripts/tests/test_public_docs_workflow.py
+++ b/scripts/tests/test_public_docs_workflow.py
@@ -25,6 +25,7 @@ SAFETY_STEP = "Exercise backup safety and diagnostic recipes"
TESTS = (
"test_production_rollout_docs.py",
"test_pmg_docs.py",
+ "test_pbs_docs.py",
"test_pve_backup_troubleshooting_docs.py",
"test_vm_disk_diagnostics.py",
"test_memory_troubleshooting_docs.py",