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
Scope TrueNAS release notes to the delivered fixes
pulse-triage[bot]e0714ad8fee4
diff --git a/docs/releases/RELEASE_NOTES_v6.6.0-rc.6.md b/docs/releases/RELEASE_NOTES_v6.6.0-rc.6.mdindex 6ba5f14d5b..a7bea40e65 100644--- a/docs/releases/RELEASE_NOTES_v6.6.0-rc.6.md+++ b/docs/releases/RELEASE_NOTES_v6.6.0-rc.6.md@@ -72,7 +72,7 @@ Pulse v6.6.0 puts alerts, charts and useful next steps together so you can see w## TrueNAS, vSphere and Docker- **TrueNAS CORE keeps usable inventory.** Unknown or string-valued disk rotation rates no longer abort collection. Pool capacity can use top-level vdev statistics when flat fields are absent, while missing or conflicting readings remain unknown.-- **TrueNAS readings recover.** Native disk-temperature history works again, with a limited fallback for empty reporting results. Fractional SCALE app CPU readings keep reporting connected, and native aggregate CPU readings include idle zero.+- **TrueNAS disk history and SCALE CPU improve.** Native disk-temperature history works again, with a limited fallback for empty reporting results. Fractional SCALE app CPU readings keep reporting connected, and native aggregate CPU readings include idle zero.- **TrueNAS explains unhealthy states.** Pools and topology give concrete reasons for attention. Services and VMs distinguish intentionally stopped items from those expected to run, with status text matching its indicator.- **vSphere leads with health.** The overview highlights vCenter signals and explains datastore and network problems. Host groups use cluster names, events use vCenter descriptions, and VM records retain the correct platform.- **Slower vCenter refreshes can get more time.** PULSE_VMWARE_POLL_TIMEOUT sets the whole inventory refresh limit, with a 20-second default. Failed refreshes retain known inventory and its original last-success time.@@ -161,6 +161,7 @@ Pulse v6.6.0 puts alerts, charts and useful next steps together so you can see w## Known issues+- **TrueNAS CORE host readings remain unresolved.** CPU and memory reporting can still fail even when disk and pool inventory works. These disk-temperature and SCALE CPU fixes do not repair that CORE host-reporting request.- **Guest safety remains under investigation.** These changes do not confirm a fix for every guest freeze or Windows restart. If monitoring was stopped after a guest froze, do not restart it solely to test this beta or this release.- **Affected backups still need precautions.** Stop Pulse monitoring before a freeze-enabled backup and keep it stopped until independent checks confirm thaw, fresh writes on every backed-up filesystem and workload liveness. An OK backup does not prove thaw.- **Elevated server memory remains unresolved.** Smaller caches and reduced copying do not confirm a lower long-running baseline. Report higher steady usage as well as continued growth using existing readings at similar uptimes and workloads.diff --git a/docs/releases/RELEASE_NOTES_v6.6.0.md b/docs/releases/RELEASE_NOTES_v6.6.0.mdindex fc78de1cce..c072909090 100644--- a/docs/releases/RELEASE_NOTES_v6.6.0.md+++ b/docs/releases/RELEASE_NOTES_v6.6.0.md@@ -72,7 +72,7 @@ Pulse v6.6.0 puts alerts, charts and useful next steps together so you can see w## TrueNAS, vSphere and Docker- **TrueNAS CORE keeps usable inventory.** Unknown or string-valued disk rotation rates no longer abort collection. Pool capacity can use top-level vdev statistics when flat fields are absent, while missing or conflicting readings remain unknown.-- **TrueNAS readings recover.** Native disk-temperature history works again, with a limited fallback for empty reporting results. Fractional SCALE app CPU readings keep reporting connected, and native aggregate CPU readings include idle zero.+- **TrueNAS disk history and SCALE CPU improve.** Native disk-temperature history works again, with a limited fallback for empty reporting results. Fractional SCALE app CPU readings keep reporting connected, and native aggregate CPU readings include idle zero.- **TrueNAS explains unhealthy states.** Pools and topology give concrete reasons for attention. Services and VMs distinguish intentionally stopped items from those expected to run, with status text matching its indicator.- **vSphere leads with health.** The overview highlights vCenter signals and explains datastore and network problems. Host groups use cluster names, events use vCenter descriptions, and VM records retain the correct platform.- **Slower vCenter refreshes can get more time.** PULSE_VMWARE_POLL_TIMEOUT sets the whole inventory refresh limit, with a 20-second default. Failed refreshes retain known inventory and its original last-success time.@@ -161,6 +161,7 @@ Pulse v6.6.0 puts alerts, charts and useful next steps together so you can see w## Known issues+- **TrueNAS CORE host readings remain unresolved.** CPU and memory reporting can still fail even when disk and pool inventory works. These disk-temperature and SCALE CPU fixes do not repair that CORE host-reporting request.- **Guest safety remains under investigation.** These changes do not confirm a fix for every guest freeze or Windows restart. If monitoring was stopped after a guest froze, do not restart it solely to test this beta or this release.- **Affected backups still need precautions.** Stop Pulse monitoring before a freeze-enabled backup and keep it stopped until independent checks confirm thaw, fresh writes on every backed-up filesystem and workload liveness. An OK backup does not prove thaw.- **Elevated server memory remains unresolved.** Smaller caches and reduced copying do not confirm a lower long-running baseline. Report higher steady usage as well as continued growth using existing readings at similar uptimes and workloads.diff --git a/scripts/release_control/render_release_body_test.py b/scripts/release_control/render_release_body_test.pyindex b5af8ee970..34159362f9 100644--- a/scripts/release_control/render_release_body_test.py+++ b/scripts/release_control/render_release_body_test.py@@ -33,6 +33,26 @@ def _discover_rc_draft_packet_paths() -> tuple[str, ...]:class RenderReleaseBodyTest(unittest.TestCase):+ def test_660_notes_scope_truenas_fixes_without_claiming_core_host_recovery(self) -> None:+ for version in ("6.6.0", "6.6.0-rc.6"):+ with self.subTest(version=version):+ notes = (_REPO_ROOT / f"docs/releases/RELEASE_NOTES_v{version}.md").read_text()+ render_release_body.validate_release_notes_shape(notes, version)+ changes = notes.split("## TrueNAS, vSphere and Docker\n", 1)[1].split("\n## ", 1)[0]+ self.assertIn("**TrueNAS disk history and SCALE CPU improve.**", changes)+ self.assertNotIn("**TrueNAS readings recover.**", notes)+ for retained in (+ "Native disk-temperature history works again",+ "limited fallback for empty reporting results",+ "Fractional SCALE app CPU readings keep reporting connected",+ "native aggregate CPU readings include idle zero",+ ):+ self.assertIn(retained, changes)+ known_issues = notes.split("## Known issues\n", 1)[1].split("\n## ", 1)[0]+ self.assertIn("**TrueNAS CORE host readings remain unresolved.**", known_issues)+ self.assertIn("CPU and memory reporting can still fail", known_issues)+ self.assertIn("do not repair that CORE host-reporting request", known_issues)+def test_beta_two_notes_describe_included_outcomes_not_the_fallback(self) -> None:notes = (_REPO_ROOT / "docs/releases/RELEASE_NOTES_v6.6.0-beta.2.md").read_text()render_release_body.validate_release_notes_shape(notes, "6.6.0-beta.2")