I am wanting to use the DiskFreeSpace monitor, but it appears that the warning levels are reversed. I applied it to a server that I monitor, and it immediately went to critical. When I look at the drive space available on that server, I see that the C: drive has 82% Free Space and the D: drive has 92% Free Space. If I drill down on the monitor, I see PercentFreeSpace = 92.00. Thus, I am guessing that it is looking at the D: drive, but why would 92% free Space be considered Critical? Also, how do I get it to monitor both the C: and D: drives? TIA, Jon

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Application Monitor Templates -DiskFreeSpace

I am wanting to use the DiskFreeSpace monitor, but it appears that the warning levels are reversed. I applied it to a server that I monitor, and it immediately went to critical. When I look at the drive space available on that server, I see that the C: drive has 82% Free Space and the drive has 92% Free Space. If I drill down on the monitor, I see PercentFreeSpace = 92.00. Thus, I am guessing that it is looking at the drive, but why would 92% free Space be considered Critical? Also, how do I get it to monitor both the C: and drives?

TIA,

Jon

Find more posts tagged with

Accepted answers

All comments

FormerMember

APM 2.0, thresholds are triggered if the value of the statistics is greater than the threshold. We'll make that configurable in 2.5.

irishjd

I guess that I am confussed then. If I look at the template itself, I see the following entries:

PercentFreeSpace

Component Type:	WMI Performance Counter Monitor
Credential for Monitoring:	MSLS BLUETEAM	Override Template
Polling Frequency:	seconds 300 seconds	Override Template
Polling Timeout:	seconds 300 seconds	Override Template
WQL Query:	SELECT PercentFreeSpace FROM Win32_PerfFormattedData_PerfDisk_LogicalDisk WHERE Name='_Total'	Override Template
Response Time Warning Threshold:	<not set>	Override Template
Response Time Critical Threshold:	<not set>	Override Template
Statistic Warning Threshold:	25.00	Override Template
Statistic Critical Threshold:	10.00	Override Template

The actuall value for PercentFreeSpace is:

PercentFreeSpace

N/A

91.00

30 ms

Thus, if I have 91% free space, and the warning threshold is 25% free space, why is the status Critical?

Jon

josh.clark

In APM 2.0, the thresholds are applied from worst to best. That is, we check if 91 > the critical value first. It is so we are done, the status is critical.

irishjd

Unfortunately, for this type of check, that logic is reversed. Higher numbers are better than lower numbers. Thus, the check should be if 91 < the critical value. If so, then it should be considered Critical. Can this be corrected in the template somehow?