diff options
| author |  Christian Hesse <mail@eworm.de> | 2023-10-24 16:26:14 +0200 |
|---|---|---|
| committer | Christian Hesse <mail@eworm.de> | 2023-10-24 17:03:12 +0200 |
| commit | ff35f0c87f4dc9ea75b2e911d9cb397ab2c120f7 (patch) | |
| tree | 7a89d42da1b24ea662c9a2171ad21400a7ce7944 /doc/check-health.md | |
| parent | d4e5194a65b5a40ce458382d28b8af45086b80f7 (diff) | |
check-health: reverse logic for RAM (free -> utilization)...
... to bring it in sync with CPU utilization.
Also make the output more verbose, at least for the warning.
---- ✂️ ----
🗃️📈️ Health warning: RAM utilization
The RAM utilization on MikroTik is at 81%!
total: 64 MiB
used: 52 MiB
free: 11 MiB
---- ✂️ ----
🗃️📉️ Health recovery: RAM utilization
The RAM utilization on MikroTik decreased to 65%.
---- ✂️ ----
Diffstat (limited to 'doc/check-health.md')
| -rw-r--r-- | doc/check-health.md | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/check-health.md b/doc/check-health.md index 34b5faf..3bde4e9 100644 --- a/doc/check-health.md +++ b/doc/check-health.md @@ -13,7 +13,7 @@ This script is run from scheduler periodically, sending notification on health related events: * high CPU utilization -* low available free RAM +* high RAM utilization (low available RAM) * voltage jumps up or down more than configured threshold * voltage drops below hard lower limit * power supply failed or recovered @@ -21,9 +21,9 @@ health related events: Note that bad initial state will not trigger an event. -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: +Monitoring CPU and RAM utilization (available processing and memory +resources) works on all devices. Other than that only sensors available +in hardware can be checked. See what your hardware supports: /system/health/print; @@ -34,10 +34,10 @@ your hardware supports:   -#### Available free RAM +#### RAM utilization (low available RAM) - - + + #### Voltage |