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
Make existing extra-temperature and fan readings discoverable
pulse-triage[bot]6549ea6921e9
diff --git a/docs/TEMPERATURE_MONITORING.md b/docs/TEMPERATURE_MONITORING.mdindex 7ea4b53d52..f6d1b598d9 100644--- a/docs/TEMPERATURE_MONITORING.md+++ b/docs/TEMPERATURE_MONITORING.md@@ -35,6 +35,32 @@ Notes:before changing its setup. A current server does not upgrade every agent.- When a Proxmox host has recent usable agent temperature data, Pulse treats the agent as the source of truth and does not also try SSH temperature collection for that host.+### Other Linux sensors and fan readings++The overview's CPU temperature is not the full agent sensor list. On+**Machines**, open the affected machine, expand **Details**, then **Machine →+Show details**, and look for **Thermals**. For a merged Proxmox entry, the+inner section is labelled **Host → Show host** instead. This card can show+other temperatures and current fan RPM already present in the agent report;+no SSH setup, driver change or additional permission is needed to open it.++With usable `sensors -j` output, the Linux agent also retains positive+non-CPU temperatures below 150 °C and positive fan RPM. Labels combine the+chip type and sensor label: an applesmc `TB0T` reading can appear as+**Applesmc Tb0t**, rather than **Battery**. Interpret chip-specific labels+using that hardware's documentation; Pulse does not identify every sensor's+physical location. A missing row is not a zero reading, and this is not an+inventory of every `hwmon` file: the direct sysfs fallback is CPU/SoC-only.++The card is a reading list, not a sensor picker. It does not offer friendly-name+editing, fan min/max, a separate History series or an alert threshold for each+extra sensor, or selection of a different sensor for the CPU row. CPU+temperature History and CPU alerts remain CPU readings; a battery temperature+must not be treated as CPU temperature. Seeing a battery reading here does not+mean Pulse will alert on it. If a needed reading is absent, use the+[existing-reading guidance](#check-existing-linux-readings-safely), not another+agent install or wider host access.+### Check existing Linux readings safelyUse the monitored host's trusted local console, not the Pulse LXC or container.diff --git a/frontend-modern/public/docs/TEMPERATURE_MONITORING.md b/frontend-modern/public/docs/TEMPERATURE_MONITORING.mdindex 7ea4b53d52..f6d1b598d9 100644--- a/frontend-modern/public/docs/TEMPERATURE_MONITORING.md+++ b/frontend-modern/public/docs/TEMPERATURE_MONITORING.md@@ -35,6 +35,32 @@ Notes:before changing its setup. A current server does not upgrade every agent.- When a Proxmox host has recent usable agent temperature data, Pulse treats the agent as the source of truth and does not also try SSH temperature collection for that host.+### Other Linux sensors and fan readings++The overview's CPU temperature is not the full agent sensor list. On+**Machines**, open the affected machine, expand **Details**, then **Machine →+Show details**, and look for **Thermals**. For a merged Proxmox entry, the+inner section is labelled **Host → Show host** instead. This card can show+other temperatures and current fan RPM already present in the agent report;+no SSH setup, driver change or additional permission is needed to open it.++With usable `sensors -j` output, the Linux agent also retains positive+non-CPU temperatures below 150 °C and positive fan RPM. Labels combine the+chip type and sensor label: an applesmc `TB0T` reading can appear as+**Applesmc Tb0t**, rather than **Battery**. Interpret chip-specific labels+using that hardware's documentation; Pulse does not identify every sensor's+physical location. A missing row is not a zero reading, and this is not an+inventory of every `hwmon` file: the direct sysfs fallback is CPU/SoC-only.++The card is a reading list, not a sensor picker. It does not offer friendly-name+editing, fan min/max, a separate History series or an alert threshold for each+extra sensor, or selection of a different sensor for the CPU row. CPU+temperature History and CPU alerts remain CPU readings; a battery temperature+must not be treated as CPU temperature. Seeing a battery reading here does not+mean Pulse will alert on it. If a needed reading is absent, use the+[existing-reading guidance](#check-existing-linux-readings-safely), not another+agent install or wider host access.+### Check existing Linux readings safelyUse the monitored host's trusted local console, not the Pulse LXC or container.diff --git a/frontend-modern/src/features/docs/__tests__/temperatureFAQ.test.ts b/frontend-modern/src/features/docs/__tests__/temperatureFAQ.test.tsindex 5343c8c2f5..6c4a87f311 100644--- a/frontend-modern/src/features/docs/__tests__/temperatureFAQ.test.ts+++ b/frontend-modern/src/features/docs/__tests__/temperatureFAQ.test.ts@@ -96,4 +96,34 @@ describe('shipped temperature FAQ', () => {);}});++ it('makes the existing extra-sensor view findable without promising battery alerts', () => {+ const guide = document.createElement('article');+ guide.innerHTML = renderDocMarkdown(+ readFileSync(path.join(servedDocs, 'TEMPERATURE_MONITORING.md'), 'utf8'),+ 'TEMPERATURE_MONITORING',+ );+ const heading = guide.querySelector('#other-linux-sensors-and-fan-readings');+ expect(heading).not.toBeNull();+ const section = document.createElement('section');+ for (let next = heading!.nextElementSibling; next; next = next.nextElementSibling) {+ if (/^H[1-6]$/.test(next.tagName)) break;+ section.appendChild(next.cloneNode(true));+ }+ const text = prose(section);+ expect(text).toContain('Machines');+ expect(text).toContain('Machine → Show details');+ expect(text).toContain('Host → Show host');+ expect(text).toContain('Thermals');+ expect(text).toContain('Applesmc Tb0t');+ expect(text).toContain('direct sysfs fallback is CPU/SoC-only');+ expect(text).toContain('not a sensor picker');+ expect(text).toContain('fan min/max');+ expect(text).toContain('does not mean Pulse will alert on it');+ expect(section.querySelector('pre, table')).toBeNull();+ expect(section.querySelector('a')?.getAttribute('href')).toBe(+ '/docs/TEMPERATURE_MONITORING#check-existing-linux-readings-safely',+ );+ expect(section.querySelector('a')?.hasAttribute('data-doc-link')).toBe(true);+ });});