Server Memory Monitoring
This task warns that RAM usage on the server is becoming dangerously high.
This task type requires PRO plan.
When to use
- When the server may degrade due to lack of RAM.
- When you want to see the trend towards memory overflow in advance.
When to choose another type
- If you only need external site availability check, use HTTP or Ping.
- If you cannot install a server script, this type won't work.
Form fields
| Field | What it means | What to specify | Example |
|---|---|---|---|
| Name | Name of the check. | Specify for which server the memory is being checked. | Production server memory |
| Group | Allows assigning the task to a project or section. | Select a group if you want to keep project tasks together. | Main project |
| Max memory, % | Memory usage threshold for alert. | Specify the value after which the server is considered overloaded with memory. | 90 |
| Timeout | Acceptable delay in data arrival. | Leave a margin for normal script execution. | 5 minutes |
| Interval | How often you expect the script to run. | The interval should match the actual script schedule. | 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 to receive an overview without manual panel access. | Weekly report |
When the alert will trigger
- If memory usage exceeds the set threshold.
- If the 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 for 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 a prolonged failure. |
"Delay" and "Repeat" parameters do not affect UP events and recovery notifications.