Disk Space #757

Open
opened 2026-04-05 16:22:47 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @AndersonOuverney on 8/6/2024

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

*Originally created by @AndersonOuverney on 8/6/2024* **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](https://github.com/user-attachments/assets/f1dd57b3-daa9-4d72-91c0-d49dc4e4dc6a) **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
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#757