You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I create a new server monitor and then create a monitoring criterion, when I want to monitor the free disk space, the monitors are not being activated.
In the tests I was able to perform, what I understood is that the conditions are the opposite.
To Reproduce
Steps to reproduce the behavior:
To reproduce, we can navigate to a server monitor and go to the criteria option.
Let's edit the criteria.
I added anything to the criteria name, the description is also not relevant in this case.
Filter condition, I checked ANY.
Filter Type = DISK USAGE (IN %)
Disk Path = /home
CHECK = evaluate this criteria over a period of time
Evaluate = All Values
For the last (in minutes) = 10 minutes
Filter Condition = Greater Than
Value = 70
Expected behavior
I expected that if the disk is more than 70% used in /home in the last 10 minutes, it would trigger the incident.
Screenshots
Desktop (please complete the following information):
OS: Fedora Linux 40
Browser Google Chrome
Version 127.0.6533.88
Deployment Type
Docker self hosted Dashboard: 7.0.2903
The text was updated successfully, but these errors were encountered:
Describe the bug
When I create a new server monitor and then create a monitoring criterion, when I want to monitor the free disk space, the monitors are not being activated.
In the tests I was able to perform, what I understood is that the conditions are the opposite.
To Reproduce
Steps to reproduce the behavior:
To reproduce, we can navigate to a server monitor and go to the criteria option.
Let's edit the criteria.
I added anything to the criteria name, the description is also not relevant in this case.
Filter condition, I checked ANY.
Filter Type = DISK USAGE (IN %)
Disk Path = /home
CHECK = evaluate this criteria over a period of time
Evaluate = All Values
For the last (in minutes) = 10 minutes
Filter Condition = Greater Than
Value = 70
Expected behavior
I expected that if the disk is more than 70% used in /home in the last 10 minutes, it would trigger the incident.
Screenshots
Desktop (please complete the following information):
Deployment Type
Docker self hosted Dashboard: 7.0.2903
The text was updated successfully, but these errors were encountered: