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
Distinguish TrueNAS disk activity and ARC composition in Help
pulse-triage[bot]d524e5385ed4
diff --git a/docs/TROUBLESHOOTING.md b/docs/TROUBLESHOOTING.mdindex f16dcf9f53..5b52b1eb0e 100644--- a/docs/TROUBLESHOOTING.md+++ b/docs/TROUBLESHOOTING.md@@ -47,7 +47,9 @@ establish safe recovery.Do not rename, remove or re-enrol resources to create evidence.- **TrueNAS readings are stale or absent:** use[TrueNAS data checks](TRUENAS.md#stale-truenas-data), keeping the platform API- and Pulse Agent paths separate.+ and Pulse Agent paths separate. If only some readings return, distinguish+ [host totals from individual disk activity](TRUENAS.md#host-totals-and-individual-disk-activity)+ and [memory usage from ARC cache](TRUENAS.md#memory-usage-and-arc-cache).- **PBS is Active but missing from monitoring:** distinguish the[server, backup inventory and History](PBS.md#pbs-is-active-but-missing-from-monitoring).An Active API connection does not establish a visible PBS resource; installingdiff --git a/docs/TRUENAS.md b/docs/TRUENAS.mdindex 5e08d4cff3..109a457f84 100644--- a/docs/TRUENAS.md+++ b/docs/TRUENAS.md@@ -430,6 +430,47 @@ TrueNAS versions, and the relevant sanitized evidence above. Do not replacean otherwise working key or clear stored History merely because a graph isempty.+#### Host totals and individual disk activity++In **TrueNAS → Overview**, a host **Disk I/O** total does not establish that+every physical disk was measured. In **TrueNAS → Storage**, check each disk's+**Activity** and **Disk I/O** separately. A temperature reading, disk inventory+or correct pool/dataset capacity does not establish live disk activity: capacity+measures space, not a read/write rate. A blank or dash is unavailable evidence,+not proof that the disk is idle.++Use TrueNAS's own **Reporting** view for missing activity. Compare the same+appliance, disk and time window; a boot disk's rate and a data pool's rate are+not interchangeable. Keep any boot-pool name already supplied in a report,+but do not rename `freenas-boot` or `boot-pool`, recreate the connection or+install an agent just to make the readings appear.++#### Memory usage and ARC cache++In **TrueNAS → Overview**, the memory bar's percentage alone does not explain+its composition. On desktop, hover over the bar to read its breakdown:++- **Used** excludes separately supplied reclaimable ARC cache.+- **Reclaimable cache** is shown when a separate cache value is available.+ **Used with ARC cache** includes that cache; do not add it again.+- **Free** is the remaining space after Used and the supplied cache, not an+ additional allocation.++An absent cache row does not establish that ARC is zero. CORE's native+**Active**, **Inactive**, **Wired**, **Laundry** and **Free** categories are+not each an ARC measurement. If your installed build does not expose the+breakdown with your keyboard or touch input, or supplies only a percentage,+use TrueNAS's own **Reporting** view instead; do not infer a missing value.++Check **History** separately from the current Overview and Storage readings.+A recovered current value does not establish that its historical series is+available or that earlier missing samples were recovered. Keep existing+versions, affected panels and original times in the same report; no new graph+capture, Debug logging, History deletion or connection change is needed just+to describe these differences.++#### Requested CORE graph evidence+If a maintainer requests a **CORE 13 native graph response**, use your existingsigned-in **TrueNAS** browser session, not the Pulse page:diff --git a/frontend-modern/public/docs/TROUBLESHOOTING.md b/frontend-modern/public/docs/TROUBLESHOOTING.mdindex f16dcf9f53..5b52b1eb0e 100644--- a/frontend-modern/public/docs/TROUBLESHOOTING.md+++ b/frontend-modern/public/docs/TROUBLESHOOTING.md@@ -47,7 +47,9 @@ establish safe recovery.Do not rename, remove or re-enrol resources to create evidence.- **TrueNAS readings are stale or absent:** use[TrueNAS data checks](TRUENAS.md#stale-truenas-data), keeping the platform API- and Pulse Agent paths separate.+ and Pulse Agent paths separate. If only some readings return, distinguish+ [host totals from individual disk activity](TRUENAS.md#host-totals-and-individual-disk-activity)+ and [memory usage from ARC cache](TRUENAS.md#memory-usage-and-arc-cache).- **PBS is Active but missing from monitoring:** distinguish the[server, backup inventory and History](PBS.md#pbs-is-active-but-missing-from-monitoring).An Active API connection does not establish a visible PBS resource; installingdiff --git a/frontend-modern/public/docs/TRUENAS.md b/frontend-modern/public/docs/TRUENAS.mdindex 5e08d4cff3..109a457f84 100644--- a/frontend-modern/public/docs/TRUENAS.md+++ b/frontend-modern/public/docs/TRUENAS.md@@ -430,6 +430,47 @@ TrueNAS versions, and the relevant sanitized evidence above. Do not replacean otherwise working key or clear stored History merely because a graph isempty.+#### Host totals and individual disk activity++In **TrueNAS → Overview**, a host **Disk I/O** total does not establish that+every physical disk was measured. In **TrueNAS → Storage**, check each disk's+**Activity** and **Disk I/O** separately. A temperature reading, disk inventory+or correct pool/dataset capacity does not establish live disk activity: capacity+measures space, not a read/write rate. A blank or dash is unavailable evidence,+not proof that the disk is idle.++Use TrueNAS's own **Reporting** view for missing activity. Compare the same+appliance, disk and time window; a boot disk's rate and a data pool's rate are+not interchangeable. Keep any boot-pool name already supplied in a report,+but do not rename `freenas-boot` or `boot-pool`, recreate the connection or+install an agent just to make the readings appear.++#### Memory usage and ARC cache++In **TrueNAS → Overview**, the memory bar's percentage alone does not explain+its composition. On desktop, hover over the bar to read its breakdown:++- **Used** excludes separately supplied reclaimable ARC cache.+- **Reclaimable cache** is shown when a separate cache value is available.+ **Used with ARC cache** includes that cache; do not add it again.+- **Free** is the remaining space after Used and the supplied cache, not an+ additional allocation.++An absent cache row does not establish that ARC is zero. CORE's native+**Active**, **Inactive**, **Wired**, **Laundry** and **Free** categories are+not each an ARC measurement. If your installed build does not expose the+breakdown with your keyboard or touch input, or supplies only a percentage,+use TrueNAS's own **Reporting** view instead; do not infer a missing value.++Check **History** separately from the current Overview and Storage readings.+A recovered current value does not establish that its historical series is+available or that earlier missing samples were recovered. Keep existing+versions, affected panels and original times in the same report; no new graph+capture, Debug logging, History deletion or connection change is needed just+to describe these differences.++#### Requested CORE graph evidence+If a maintainer requests a **CORE 13 native graph response**, use your existingsigned-in **TrueNAS** browser session, not the Pulse page: