ignace/cheap_system_monitor
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

graphing optimized

Browse Source
This commit is contained in:
ignace
2026-08-12 08:14:38 +02:00
parent 177c7479b6
commit 0fd16034d9
3 changed files with 41 additions and 49 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+12 -11
View File
@@ -77,18 +77,19 @@ sources. Temperature is read from Linux thermal zones. Active Raspberry Pi
throttling is read with `vcgencmd`; it appears as unknown on other systems.
Failed services are counted with `systemctl`. OOM kills come from the kernel's
cumulative `/proc/vmstat` counter and are graphed as events per minute.
Storage-health graphs show available space in GiB and inode consumption for
each configured mountpoint. A read-only filesystem is shown at 100% on the
status graph. I/O wait is included in the CPU graph. These portable indicators
work with SD cards and USB drives without requiring SMART support.
Available space, inode consumption, and read-only state are retained as inputs
to the per-mountpoint health score rather than displayed as separate graphs.
I/O wait is included in the CPU graph. These portable indicators work with SD
cards and USB drives without requiring SMART support.
The storage operational-health score summarizes the worst configured
mountpoint. A score of 10 means no current problem is visible, while a
read-only filesystem scores 0. Space and inode usage begin reducing the score
above 75%; either reaches 0 when exhausted. I/O wait above 10% can subtract up
to three points. This is an operational-risk score, not a measurement of flash
wear or remaining media life; SD cards and many USB bridges do not expose the
hardware data needed to estimate those reliably.
The storage operational-health graph shows one score for each configured
mountpoint. A score of 10 means no current problem is visible, while a read-only
filesystem scores 0. Space and inode usage begin reducing that filesystem's
score above 75%; either reaches 0 when exhausted. Host-wide I/O wait above 10%
can subtract up to three points from every score because Linux's CPU wait metric
cannot attribute the delay to one mountpoint. This is an operational-risk score,
not a measurement of flash wear or remaining media life; SD cards and many USB
bridges do not expose the hardware data needed to estimate those reliably.
## Run from the source tree