adfded temperature, failed services and disk health

This commit is contained in:
2026-08-12 07:59:29 +02:00
parent 413543ca84
commit 177c7479b6
3 changed files with 215 additions and 23 deletions
+24 -3
View File
@@ -12,6 +12,11 @@ It collects:
- disk usage for `/` and up to two additional mountpoints
- memory usage
- system uptime in days
- CPU temperature and active Raspberry Pi throttling
- failed systemd services and kernel out-of-memory kills
- available filesystem space, inode usage, and read-only filesystem state
- CPU I/O wait
- a combined storage operational-health score from 0 to 10
## Install
@@ -65,9 +70,25 @@ installation naturally needs time to accumulate history; RRD archives are
consolidated to five-minute samples for two weeks and hourly samples for a year.
The RRD schema is fixed when the database is created. When upgrading from a
version without uptime monitoring, move or remove the existing `system.rrd`
before the next collection if preserving its old history is not required. The
collector will then create a new database containing the uptime data source.
version without the latest monitoring data sources, move or remove the
existing `system.rrd` before the next collection if preserving its old history
is not required. The collector will then create a database with the new data
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.
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.
## Run from the source tree