Server Load Average monitoring
This task helps detect Linux server overload by average system load, not just CPU percentage.
This task type requires PRO plan.
Form Fields
| Field | What it means | What to specify | Example |
|---|---|---|---|
| Name | Name of the check. | Specify for which server the average load is monitored. | Load Average production-server |
| Group | Allows assigning the task to a project or section. | Select a group if you want to keep project tasks together. | Main project |
| Max Load Average | Average load threshold for alert. | Specify value considering number of cores and usual server load. | 4 |
| Timeout | Acceptable delay for data arrival from script. | Leave margin for normal script execution. | 5 minutes |
| Interval | How often the load value will arrive. | Select frequency matching script launch. | 1 minute |
| Notification Channels | Where to send problem and recovery messages. | Check channels where you actually read notifications. | Telegram and email |
| Reports | Periodic task summaries. | Enable if you want overview without manual panel login. | Weekly report |
When Alert Triggers
- If Load Average exceeds the specified threshold.
- If server script fails to send data on time.
Notification Settings
For each notification channel in the task, additional parameters can be set. They apply only to DOWN events.
| Parameter | What it does |
|---|---|
| Enabled | Allows or disables sending notifications via this channel for this task. |
| Delay for PRO | Delays the first DOWN notification by selected time (up to 12 hours). Convenient to avoid alerts for short-term failures. |
| Repeat after PRO | Periodically repeats notification while task remains in DOWN status (up to 1 hour between repeats). Suitable when important not to miss prolonged failure. |
"Delay" and "Repeat" parameters do not affect UP events and recovery notifications.