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.

Explain per-VM memory alert Off without implying metric hiding

pulse-triage[bot]0b07093f1ca9
diff --git a/docs/CONFIGURATION.md b/docs/CONFIGURATION.md
index a89c89d910..9fca27bca8 100644
--- a/docs/CONFIGURATION.md
+++ b/docs/CONFIGURATION.md
@@ -537,6 +537,19 @@ For numeric metric rules such as CPU, memory and disk usage:
| Blank per-resource metric value | Inherits the group default; it does **not** mean Off. An inherited Off default remains Off. |
| Saved numeric metric trigger `0` or a negative value | Disables that metric rule. Zero does **not** mean “alert on any usage”. Older saved rules may use `0`; the current metric Off control writes `-1`. |
+**Metric Off is not a metric-hiding control.** The reading remains visible; Off
+does not mark it **ignored** or **N/A**, nor prove that the workload is healthy.
+For an appliance VM whose hypervisor memory reading does not represent useful
+guest memory pressure, turn off only that VM's **Memory** metric rule if those
+alerts are unwanted. Keep its CPU, disk, backup and uptime monitoring in place;
+do not disable the whole resource or global alerts to quiet one metric.
+
+A near-100% hypervisor memory reading alone does not establish guest memory
+pressure or an appliance fault. Check the appliance's own ordinary status where
+available. Do not install an agent, restart the VM or change its configuration
+solely to remove the reading. Pulse has no per-VM control here to replace one
+metric with an explicitly ignored reading.
+
**Zero has different meanings in different fields.** A zero *metric trigger*
disables the rule, but zero *powered-off tolerance* below means immediate
eligibility on an authoritative stopped observation. Do not copy one field's
diff --git a/frontend-modern/public/docs/CONFIGURATION.md b/frontend-modern/public/docs/CONFIGURATION.md
index a89c89d910..9fca27bca8 100644
--- a/frontend-modern/public/docs/CONFIGURATION.md
+++ b/frontend-modern/public/docs/CONFIGURATION.md
@@ -537,6 +537,19 @@ For numeric metric rules such as CPU, memory and disk usage:
| Blank per-resource metric value | Inherits the group default; it does **not** mean Off. An inherited Off default remains Off. |
| Saved numeric metric trigger `0` or a negative value | Disables that metric rule. Zero does **not** mean “alert on any usage”. Older saved rules may use `0`; the current metric Off control writes `-1`. |
+**Metric Off is not a metric-hiding control.** The reading remains visible; Off
+does not mark it **ignored** or **N/A**, nor prove that the workload is healthy.
+For an appliance VM whose hypervisor memory reading does not represent useful
+guest memory pressure, turn off only that VM's **Memory** metric rule if those
+alerts are unwanted. Keep its CPU, disk, backup and uptime monitoring in place;
+do not disable the whole resource or global alerts to quiet one metric.
+
+A near-100% hypervisor memory reading alone does not establish guest memory
+pressure or an appliance fault. Check the appliance's own ordinary status where
+available. Do not install an agent, restart the VM or change its configuration
+solely to remove the reading. Pulse has no per-VM control here to replace one
+metric with an explicitly ignored reading.
+
**Zero has different meanings in different fields.** A zero *metric trigger*
disables the rule, but zero *powered-off tolerance* below means immediate
eligibility on an authoritative stopped observation. Do not copy one field's
diff --git a/frontend-modern/src/utils/__tests__/metricThresholdHelp.test.ts b/frontend-modern/src/utils/__tests__/metricThresholdHelp.test.ts
index 18ffba86f1..c617ed22f9 100644
--- a/frontend-modern/src/utils/__tests__/metricThresholdHelp.test.ts
+++ b/frontend-modern/src/utils/__tests__/metricThresholdHelp.test.ts
@@ -22,6 +22,33 @@ function article() {
}
describe('existing metric threshold help', () => {
+ it('distinguishes a per-VM memory alert override from hiding or ignoring a reading', () => {
+ const text = article().textContent?.replace(/\s+/g, ' ');
+ expect(text).toContain('Metric Off is not a metric-hiding control');
+ expect(text).toContain('The reading remains visible');
+ expect(text).toContain('does not mark it ignored or N/A');
+ expect(text).toContain("turn off only that VM's Memory metric rule");
+ expect(text).toContain('Keep its CPU, disk, backup and uptime monitoring in place');
+ expect(text).toContain('do not disable the whole resource or global alerts');
+ expect(text).toContain('alone does not establish guest memory pressure or an appliance fault');
+ expect(text).toContain('Do not install an agent, restart the VM or change its configuration');
+ expect(text).toContain('no per-VM control here to replace one metric');
+
+ const resource = {
+ id: 'appliance-vm',
+ name: 'Appliance VM',
+ thresholds: { memory: -1 },
+ defaults: { memory: 85, cpu: 80 },
+ };
+ expect(
+ isAlertResourceMetricOff(
+ getAlertResourceMetricDisplayValue(resource, 'memory', {}, false),
+ ),
+ ).toBe(true);
+ expect(getAlertResourceMetricDisplayValue(resource, 'cpu', {}, false)).toBe(80);
+ expect(article().querySelector('pre')).toBeNull();
+ });
+
it('renders Off and inheritance separately, matching the live editor model', () => {
const rows = [...article().querySelectorAll('tbody tr')].map((row) =>
row.textContent?.replace(/\s+/g, ' '),