Server CPU Monitoring
This task monitors CPU load based on data sent by a script from your server.
This task type requires the PRO plan.
When to use
- When high CPU load can lead to service degradation or process hanging.
- When you want to receive notifications for anomalous CPU load.
When to choose another type
- If you only need external availability checks, choose HTTP, Ping, or Port.
- If you cannot run a server script, this type is not suitable.
Form fields
| Field | What it means | What to specify | Example |
|---|---|---|---|
| Name | Name of the check. | Specify which server's CPU is being monitored. | Main server CPU |
| Group | Allows assigning the task to a project or section. | Select a group if you want to keep project tasks together. | Main project |
| CPU Max, % | CPU load threshold for alert. | Specify the percentage that is already considered overload for your server. | 85 |
| Timeout | Acceptable delay in receiving data from the script. | Leave a margin for normal script execution. | 5 minutes |
| Interval | How often you expect the script to run. | Select the frequency at which the script will actually run. | 1 minute |
| Notification channels | Where to send messages about issues and recovery. | Check the channels where you actually read notifications. | Telegram and email |
| Reports | Periodic summaries for the task. | Enable if you want an overview without manual panel access. | Weekly report |
When the alert will trigger
- If CPU load exceeds the specified threshold.
- If the server script stops sending data on time.
Notification settings
For each notification channel in the task, you can set additional parameters. They only apply to DOWN events.
| Parameter | What it does |
|---|---|
| Enabled | Allows or disables sending notifications for this channel for this task. |
| Delay by PRO | Delays the first DOWN notification by the selected time (up to 12 hours). Convenient to avoid alerts for short-term failures. |
| Repeat after PRO | Periodically repeats the notification while the task remains in DOWN status (up to 1 hour between repeats). Suitable when it's important not to miss prolonged failures. |
"Delay" and "Repeat" parameters do not affect UP events and recovery notifications.