Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disk Space #1629

Open
AndersonOuverney opened this issue Aug 6, 2024 · 0 comments
Open

Disk Space #1629

AndersonOuverney opened this issue Aug 6, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@AndersonOuverney
Copy link

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
image

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

@AndersonOuverney AndersonOuverney added the bug Something isn't working label Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant