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
Explain threshold alert markers without implying recovery
pulse-triage[bot]1ae2ed30871b
diff --git a/docs/CONFIGURATION.md b/docs/CONFIGURATION.mdindex dc12695604..b632e8d192 100644--- a/docs/CONFIGURATION.md+++ b/docs/CONFIGURATION.md@@ -662,7 +662,8 @@ Manage alert rules in **Alerts → Thresholds**. Choose the platform and resourcbefore editing; a group default can affect many resources, while a customresource override takes precedence. Finish the edit and use **Save Changes**;an unsaved value is not the running policy. Reload after a successful save to-check that the intended value persisted.+check that the intended value persisted. Read the [active-alert markers](#read-active-alert-markers)+separately from the saved limits.For TrueNAS physical disks, read the [disk temperature and health guide](TRUENAS.md#disk-temperature-and-health)before changing a rule: heat, SMART faults and missing readings are different@@ -725,6 +726,28 @@ critical-alert exceptions. Check [Recent delivery activity](TROUBLESHOOTING.md#tseparately: a saved threshold or a successful destination Test does not proveordinary alert delivery.+### Read active-alert markers++A pulsing red dot titled **Active alert** beside a metric in **Alerts →+Thresholds** means the current alert list contains an open alert for that row+and metric. It is not a new reading, another threshold or proof that a+notification was delivered.++- A **Machines** row's **Disk %** or **Disk Temp** dot can come from an alert+ on one of that machine's filesystems or SMART disk temperatures. Open+ **Alerts → Overview** to identify the exact filesystem or device; the dot+ does not mean every disk is affected.+- When a Proxmox node is linked to a Pulse agent, the agent's CPU, memory and+ disk alerts appear against its **Machines** row, not the node's corresponding+ metric. Check the owning row rather than changing the node's limits.++**No dot is not proof that the workload is healthy or that no notification+failed.** Check the matching alert and its current reading in Overview;+[an open alert can outlast a falling reading](TROUBLESHOOTING.md#usage-alert-stays-open-after-the-reading-falls).+Check [Recent delivery activity](TROUBLESHOOTING.md#test-succeeds-but-real-alerts-are-missing)+separately for notification failures. Do not create load, change thresholds or+send a Test just to make a marker appear or disappear.+### VM and container powered-off toleranceOpen **Alerts → Thresholds → Alert intent & grace** to configure how long adiff --git a/frontend-modern/public/docs/CONFIGURATION.md b/frontend-modern/public/docs/CONFIGURATION.mdindex dc12695604..b632e8d192 100644--- a/frontend-modern/public/docs/CONFIGURATION.md+++ b/frontend-modern/public/docs/CONFIGURATION.md@@ -662,7 +662,8 @@ Manage alert rules in **Alerts → Thresholds**. Choose the platform and resourcbefore editing; a group default can affect many resources, while a customresource override takes precedence. Finish the edit and use **Save Changes**;an unsaved value is not the running policy. Reload after a successful save to-check that the intended value persisted.+check that the intended value persisted. Read the [active-alert markers](#read-active-alert-markers)+separately from the saved limits.For TrueNAS physical disks, read the [disk temperature and health guide](TRUENAS.md#disk-temperature-and-health)before changing a rule: heat, SMART faults and missing readings are different@@ -725,6 +726,28 @@ critical-alert exceptions. Check [Recent delivery activity](TROUBLESHOOTING.md#tseparately: a saved threshold or a successful destination Test does not proveordinary alert delivery.+### Read active-alert markers++A pulsing red dot titled **Active alert** beside a metric in **Alerts →+Thresholds** means the current alert list contains an open alert for that row+and metric. It is not a new reading, another threshold or proof that a+notification was delivered.++- A **Machines** row's **Disk %** or **Disk Temp** dot can come from an alert+ on one of that machine's filesystems or SMART disk temperatures. Open+ **Alerts → Overview** to identify the exact filesystem or device; the dot+ does not mean every disk is affected.+- When a Proxmox node is linked to a Pulse agent, the agent's CPU, memory and+ disk alerts appear against its **Machines** row, not the node's corresponding+ metric. Check the owning row rather than changing the node's limits.++**No dot is not proof that the workload is healthy or that no notification+failed.** Check the matching alert and its current reading in Overview;+[an open alert can outlast a falling reading](TROUBLESHOOTING.md#usage-alert-stays-open-after-the-reading-falls).+Check [Recent delivery activity](TROUBLESHOOTING.md#test-succeeds-but-real-alerts-are-missing)+separately for notification failures. Do not create load, change thresholds or+send a Test just to make a marker appear or disappear.+### VM and container powered-off toleranceOpen **Alerts → Thresholds → Alert intent & grace** to configure how long adiff --git a/scripts/tests/test_metric_alert_help_docs.py b/scripts/tests/test_metric_alert_help_docs.pyindex e2a3135f0b..2be23cc787 100644--- a/scripts/tests/test_metric_alert_help_docs.py+++ b/scripts/tests/test_metric_alert_help_docs.py@@ -68,6 +68,44 @@ class MetricAlertHelpDocsTest(unittest.TestCase):self.assertIn(boundary, self.guide)self.assertNotIn('```', self.guide)+ def test_threshold_marker_help_follows_both_current_consumers(self):+ source = (ROOT / 'docs/CONFIGURATION.md').read_text()+ heading = '### Read active-alert markers\n'+ self.assertEqual(source.count(heading), 1)+ self.assertIn('[active-alert markers](#read-active-alert-markers)', source)+ self.assertEqual(source.encode(),+ (ROOT / 'frontend-modern/public/docs/CONFIGURATION.md').read_bytes())+ guide = ' '.join(source.split(heading, 1)[1].split('\n### ', 1)[0].split())+ for file in ('AlertResourceTableRow.tsx', 'AlertResourceTableMobile.tsx'):+ consumer = (ROOT / 'frontend-modern/src/components/Alerts' / file).read_text()+ self.assertIn('title="Active alert"', consumer)+ self.assertIn('hasActiveAlert(', consumer)+ self.assertIn('current alert list contains an open alert for that row and metric', guide)+ self.assertIn('not a new reading, another threshold', guide)+ self.assertIn('No dot is not proof that the workload is healthy', guide)+ self.assertIn('Recent delivery activity', guide)+ self.assertIn('#usage-alert-stays-open-after-the-reading-falls', guide)+ self.assertIn('#test-succeeds-but-real-alerts-are-missing', guide)+ self.assertIn('Do not create load, change thresholds or send a Test', guide)+ self.assertNotIn('```', guide)++ def test_marker_attribution_distinguishes_machine_disks_and_linked_nodes(self):+ source = (ROOT / 'docs/CONFIGURATION.md').read_text()+ guide = ' '.join(source.split('### Read active-alert markers\n', 1)[1]+ .split('\n### ', 1)[0].split())+ model = (ROOT / 'frontend-modern/src/features/alerts/thresholds/thresholdsResourceModel.ts').read_text()+ host = (ROOT / 'frontend-modern/src/features/alerts/thresholds/hooks/useThresholdsHostData.ts').read_text()+ self.assertIn("child.startsWith('disk:') || child.startsWith('disk_temp:')", model)+ self.assertIn("row.type === 'agent' && index.byMachine", model)+ self.assertIn('alertResourceIds: uniqueIds(node.proxmox?.sourceId, node.id)', host)+ self.assertIn('agentAlertResourceId(', host)+ for boundary in ('**Disk %** or **Disk Temp**', 'exact filesystem or device',+ 'does not mean every disk is affected',+ "agent's CPU, memory and disk alerts", 'not the node',+ 'Check the owning row rather than changing the node'):+ with self.subTest(boundary=boundary):+ self.assertIn(boundary, guide)+if __name__ == '__main__':unittest.main()