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 CORE reporting rejection without repeated capture
pulse-triage[bot]6df560d47dfa
diff --git a/docs/TRUENAS.md b/docs/TRUENAS.mdindex b880b3e51e..d377c5b53b 100644--- a/docs/TRUENAS.md+++ b/docs/TRUENAS.md@@ -335,6 +335,28 @@ do not run it during a backup, freeze/thaw or an unresponsive-host incidentmerely to obtain an export. Keep the existing observations instead. See[safe diagnostics collection](TROUBLESHOOTING.md#collect-diagnostics-safely).+### CORE 13 rejects the reporting request++For **TrueNAS CORE 13**, `POST /reporting/get_data` returning HTTP **400** with+`The following attributes are not expected: query` means the appliance rejected+Pulse's reporting request format. It is not an invalid API key or evidence that+the NAS is idle. A successful **Test connection**, fresh inventory or advancing+`observed.collectedAt` does not establish that CPU, memory or History was measured.++Use TrueNAS's own **Reporting** graphs for CPU, memory and I/O while Pulse's+collection is unavailable. A displayed zero or an empty History panel alongside+this rejection is **not a measured idle value**. Do not rotate the key, recreate+the connection, install an agent, switch transport or weaken TLS verification+to address this request-format error; those actions do not correct it.++Keep the existing, locally reviewed error and affected versions in your original+report; [the CORE request-format report](https://github.com/rcourtman/Pulse/issues/2964)+tracks this failure. If versions or native graph replies are already supplied,+do not collect them again. A newer release is a reason to retest only when it+contains the relevant correction, not simply because its version is higher.+Other missing-reading failures still need their own evidence; this specific+error does not diagnose every CORE or SCALE problem.+### Inventory works but CPU, memory or History is missingServices, uptime, hardware capacity and disk temperatures can be collected@@ -343,7 +365,9 @@ does not establish a live reading; check the CPU/memory usage columns andHistory series separately. A disk-utilisation line does not establish thatCPU, memory or network History is available.-Check whether the corresponding graphs work in the TrueNAS web UI. If Pulse+If the existing error is the [CORE 13 request-format rejection](#core-13-rejects-the-reporting-request),+follow that guidance rather than collecting another graph response. Otherwise,+check whether the corresponding graphs work in the TrueNAS web UI. If Pulsestill shows missing readings, report the affected panels, running Pulse andTrueNAS versions, and the relevant sanitized evidence above. Do not replacean otherwise working key or clear stored History merely because a graph isdiff --git a/frontend-modern/public/docs/TRUENAS.md b/frontend-modern/public/docs/TRUENAS.mdindex b880b3e51e..d377c5b53b 100644--- a/frontend-modern/public/docs/TRUENAS.md+++ b/frontend-modern/public/docs/TRUENAS.md@@ -335,6 +335,28 @@ do not run it during a backup, freeze/thaw or an unresponsive-host incidentmerely to obtain an export. Keep the existing observations instead. See[safe diagnostics collection](TROUBLESHOOTING.md#collect-diagnostics-safely).+### CORE 13 rejects the reporting request++For **TrueNAS CORE 13**, `POST /reporting/get_data` returning HTTP **400** with+`The following attributes are not expected: query` means the appliance rejected+Pulse's reporting request format. It is not an invalid API key or evidence that+the NAS is idle. A successful **Test connection**, fresh inventory or advancing+`observed.collectedAt` does not establish that CPU, memory or History was measured.++Use TrueNAS's own **Reporting** graphs for CPU, memory and I/O while Pulse's+collection is unavailable. A displayed zero or an empty History panel alongside+this rejection is **not a measured idle value**. Do not rotate the key, recreate+the connection, install an agent, switch transport or weaken TLS verification+to address this request-format error; those actions do not correct it.++Keep the existing, locally reviewed error and affected versions in your original+report; [the CORE request-format report](https://github.com/rcourtman/Pulse/issues/2964)+tracks this failure. If versions or native graph replies are already supplied,+do not collect them again. A newer release is a reason to retest only when it+contains the relevant correction, not simply because its version is higher.+Other missing-reading failures still need their own evidence; this specific+error does not diagnose every CORE or SCALE problem.+### Inventory works but CPU, memory or History is missingServices, uptime, hardware capacity and disk temperatures can be collected@@ -343,7 +365,9 @@ does not establish a live reading; check the CPU/memory usage columns andHistory series separately. A disk-utilisation line does not establish thatCPU, memory or network History is available.-Check whether the corresponding graphs work in the TrueNAS web UI. If Pulse+If the existing error is the [CORE 13 request-format rejection](#core-13-rejects-the-reporting-request),+follow that guidance rather than collecting another graph response. Otherwise,+check whether the corresponding graphs work in the TrueNAS web UI. If Pulsestill shows missing readings, report the affected panels, running Pulse andTrueNAS versions, and the relevant sanitized evidence above. Do not replacean otherwise working key or clear stored History merely because a graph isdiff --git a/frontend-modern/src/features/docs/__tests__/truenasErrorGuide.test.ts b/frontend-modern/src/features/docs/__tests__/truenasErrorGuide.test.tsindex 54b7c4b1a3..ec74c6693c 100644--- a/frontend-modern/src/features/docs/__tests__/truenasErrorGuide.test.ts+++ b/frontend-modern/src/features/docs/__tests__/truenasErrorGuide.test.ts@@ -142,4 +142,44 @@ describe('shipped TrueNAS error diagnosis', () => {expect(text).toContain(boundary);}});++ it('distinguishes CORE request rejection from credentials, inventory and measured zero', () => {+ const section = sectionAt(renderGuide('TRUENAS'), '#core-13-rejects-the-reporting-request');+ const text = prose(section);+ for (const fact of [+ 'TrueNAS CORE 13',+ 'POST /reporting/get_data',+ '400',+ 'The following attributes are not expected: query',+ 'not an invalid API key',+ 'observed.collectedAt',+ 'not a measured idle value',+ "Use TrueNAS's own Reporting graphs",+ 'Do not rotate the key, recreate the connection, install an agent, switch transport or weaken TLS verification',+ 'do not collect them again',+ 'contains the relevant correction',+ 'does not diagnose every CORE or SCALE problem',+ ]) {+ expect(text).toContain(fact);+ }+ expect(section.querySelector('pre, form, input, button')).toBeNull();+ expect(section.querySelector('a')?.getAttribute('href')).toBe(+ 'https://github.com/rcourtman/Pulse/issues/2964',+ );+ });++ it('routes missing-telemetry readers to the specific rejection before new graph collection', () => {+ const article = renderGuide('TRUENAS');+ const missing = sectionAt(article, '#inventory-works-but-cpu-memory-or-history-is-missing');+ const link = missing.querySelector<HTMLAnchorElement>(+ 'a[href="#core-13-rejects-the-reporting-request"]',+ );+ expect(link?.textContent).toBe('CORE 13 request-format rejection');+ expect(link?.hasAttribute('data-doc-link')).toBe(true);+ expect(article.querySelector(link!.getAttribute('href')!)?.tagName).toBe('H3');+ expect(prose(missing)).toContain('rather than collecting another graph response');+ expect(readFileSync(path.join(repoRoot, 'docs/TRUENAS.md'), 'utf8')).toBe(+ readFileSync(path.join(repoRoot, 'frontend-modern/public/docs/TRUENAS.md'), 'utf8'),+ );+ });});