Welcome!
Component
Hub
Problem Description
I have configured the following alert for one of my systems (Windows):
CPU average exceeds 90% for 30 minutes.
This alert gets sent to me via Pushover when triggered. However, it keeps sending me this alert with seemingly random intervals until the CPU usage drops to normal usage again. This is probably caused by the fact that the CPU usage under load fluctuates between 85% and 95%. For every time it hits 90% after coming below it, it seems to start a new 30 minute trigger.
Expected Behavior
Receive alerts every X (setting) minutes for as long as the CPU averages above the set value.
In my example, every 30 minutes.
Steps to Reproduce
- Set an alert for CPU average exceeds 90% for 30 minutes
- Cause CPU load on the monitored system varying between 85% and 95%
- Observe first alert after 30 minutes
- Observe more alerts at seemingly random intervals (2 minutes, 5 minutes, 10 minutes, etc.) until CPU load goes back to normal.
OS / Architecture
Windows 11 (agent, binary), Synology docker (hub)
Beszel version
0.18.7
Installation method
Docker
Configuration
Hub Logs
No logging references this issue.
Agent Logs
No logging references this issue (including debug).
Welcome!
Component
Hub
Problem Description
I have configured the following alert for one of my systems (Windows):
CPU average exceeds 90% for 30 minutes.
This alert gets sent to me via Pushover when triggered. However, it keeps sending me this alert with seemingly random intervals until the CPU usage drops to normal usage again. This is probably caused by the fact that the CPU usage under load fluctuates between 85% and 95%. For every time it hits 90% after coming below it, it seems to start a new 30 minute trigger.
Expected Behavior
Receive alerts every X (setting) minutes for as long as the CPU averages above the set value.
In my example, every 30 minutes.
Steps to Reproduce
OS / Architecture
Windows 11 (agent, binary), Synology docker (hub)
Beszel version
0.18.7
Installation method
Docker
Configuration
Hub Logs
No logging references this issue.Agent Logs