aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/check-health.d/notification-01-cpu-load-high.avifbin6066 -> 0 bytes
-rw-r--r--doc/check-health.d/notification-01-cpu-utilization-high.avifbin0 -> 6453 bytes
-rw-r--r--doc/check-health.d/notification-02-cpu-load-ok.avifbin6378 -> 0 bytes
-rw-r--r--doc/check-health.d/notification-02-cpu-utilization-ok.avifbin0 -> 6717 bytes
-rw-r--r--doc/check-health.md14
5 files changed, 7 insertions, 7 deletions
diff --git a/doc/check-health.d/notification-01-cpu-load-high.avif b/doc/check-health.d/notification-01-cpu-load-high.avif
deleted file mode 100644
index 3c1a468..0000000
--- a/doc/check-health.d/notification-01-cpu-load-high.avif
+++ /dev/null
Binary files differ
diff --git a/doc/check-health.d/notification-01-cpu-utilization-high.avif b/doc/check-health.d/notification-01-cpu-utilization-high.avif
new file mode 100644
index 0000000..8aad878
--- /dev/null
+++ b/doc/check-health.d/notification-01-cpu-utilization-high.avif
Binary files differ
diff --git a/doc/check-health.d/notification-02-cpu-load-ok.avif b/doc/check-health.d/notification-02-cpu-load-ok.avif
deleted file mode 100644
index 4f12b70..0000000
--- a/doc/check-health.d/notification-02-cpu-load-ok.avif
+++ /dev/null
Binary files differ
diff --git a/doc/check-health.d/notification-02-cpu-utilization-ok.avif b/doc/check-health.d/notification-02-cpu-utilization-ok.avif
new file mode 100644
index 0000000..ee5d7d0
--- /dev/null
+++ b/doc/check-health.d/notification-02-cpu-utilization-ok.avif
Binary files differ
diff --git a/doc/check-health.md b/doc/check-health.md
index 850d61c..58c1fba 100644
--- a/doc/check-health.md
+++ b/doc/check-health.md
@@ -12,7 +12,7 @@ Description
This script is run from scheduler periodically, sending notification on
health related events:
-* high CPU load
+* high CPU utilization
* low available free RAM
* voltage jumps up or down more than configured threshold
* voltage drops below hard lower limit
@@ -21,18 +21,18 @@ health related events:
Note that bad initial state will not trigger an event.
-Monitoring CPU load and available free RAM works on all devices. Other
-than that only sensors available in hardware can be checked. See what your
-hardware supports:
+Monitoring CPU utilization and available free RAM works on all devices.
+Other than that only sensors available in hardware can be checked. See what
+your hardware supports:
/system/health/print;
### Sample notifications
-#### CPU load
+#### CPU utilization
-![check-health notification cpu load high](check-health.d/notification-01-cpu-load-high.avif)
-![check-health notification cpu load ok](check-health.d/notification-02-cpu-load-ok.avif)
+![check-health notification cpu utilization high](check-health.d/notification-01-cpu-utilization-high.avif)
+![check-health notification cpu utilization ok](check-health.d/notification-02-cpu-utilization-ok.avif)
#### Available free RAM