mirror of
https://github.com/eworm-de/routeros-scripts
synced 2024-05-14 08:04:19 +00:00
ff35f0c87f
... 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%. ---- ✂️ ----
90 lines
3.1 KiB
Markdown
90 lines
3.1 KiB
Markdown
Notify about health state
|
||
=========================
|
||
|
||
[⬅️ Go back to main README](../README.md)
|
||
|
||
> ℹ️ **Info**: This script can not be used on its own but requires the base
|
||
> installation. See [main README](../README.md) for details.
|
||
|
||
Description
|
||
-----------
|
||
|
||
This script is run from scheduler periodically, sending notification on
|
||
health related events:
|
||
|
||
* high CPU utilization
|
||
* 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
|
||
* temperature is above or below threshold
|
||
|
||
Note that bad initial state will not trigger an event.
|
||
|
||
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;
|
||
|
||
### Sample notifications
|
||
|
||
#### CPU utilization
|
||
|
||
|
||
|
||
|
||
#### RAM utilization (low available RAM)
|
||
|
||
|
||
|
||
|
||
#### Voltage
|
||
|
||
|
||
|
||
#### Temperature
|
||
|
||
|
||
|
||
|
||
#### PSU state
|
||
|
||
|
||
|
||
|
||
Requirements and installation
|
||
-----------------------------
|
||
|
||
Just install the script and create a scheduler:
|
||
|
||
$ScriptInstallUpdate check-health;
|
||
/system/scheduler/add interval=53s name=check-health on-event="/system/script/run check-health;" start-time=startup;
|
||
|
||
> ℹ️ **Info**: Running lots of scripts simultaneously can tamper the
|
||
> precision of cpu utilization, escpecially on devices with limited
|
||
> resources. Thus an unusual interval is used here.
|
||
|
||
Configuration
|
||
-------------
|
||
|
||
The configuration goes to `global-config-overlay`, these are the parameters:
|
||
|
||
* `CheckHealthTemperature`: an array specifying temperature thresholds for sensors
|
||
* `CheckHealthVoltageLow`: value (in volt*10) giving a hard lower limit
|
||
* `CheckHealthVoltagePercent`: percentage value to trigger voltage jumps
|
||
|
||
> ℹ️ **Info**: Copy relevant configuration from
|
||
> [`global-config`](../global-config.rsc) (the one without `-overlay`) to
|
||
> your local `global-config-overlay` and modify it to your specific needs.
|
||
|
||
Also notification settings are required for
|
||
[e-mail](mod/notification-email.md),
|
||
[matrix](mod/notification-matrix.md),
|
||
[ntfy](mod/notification-ntfy.md) and/or
|
||
[telegram](mod/notification-telegram.md).
|
||
|
||
---
|
||
[⬅️ Go back to main README](../README.md)
|
||
[⬆️ Go back to top](#top)
|