SolarWinds uses cookies on our websites to facilitate and improve your online experience. By continuing to use our website, you consent to our use of cookies. For further details on cookies, please see our cookies policy.
Hide this message
The Orion® Platform Instructor-led Classes
Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports
Reserve your seat.
This article provides brief information and steps to resolve the issue when Disk space alert does not trigger for Exchange Servers.
2 Exchange Servers ran out of disk and no alerts were trigggered:
NPM version 11.5.2
DB Tables and Diagnostics proved R: Drive was added to some exchange Servers and on other ones it did not trigger as it was not added at that point in ti,e. G Drive triggered fine on same day.
R: Drives Added recently had much higher Volume IDs.
Example:
Exchange Servers:
NodeID | ObjectSubType | Caption | IOSVersion |
249 | WMI | AMAIL02 | Windows 2012 Server |
250 | WMI | AMAIL01 | Windows 2012 Server |
251 | WMI | BMAIL02 | Windows 2012 Server |
252 | WMI | BMAIL01 | Windows 2012 Server |
Node:
Volumes
NodeID | VolumeID | VolIndex | Caption | VolumePercentUsed | VolSpaceUsed | VolSpaceAvail | VolumeSize | Status | VolumeResponding |
111 | 2620 | 1 | Physical Memory | 19.01 | 6530150400 | 27829116928 | 34359267328 | 1 | Y |
111 | 2621 | 2 | Virtual Memory | 18.58 | 7182680064 | 31471554560 | 38654234624 | 1 | Y |
111 | 2622 | 4 | C:\ Label:OSDisk 0C07D9B0 | 83.40 | 56875360256 | 11318775808 | 68194136064 | 1 | Y |
111 | 2623 | 5 | D:\ Label: EEE31F4B | 47.71 | 20489826304 | 22456696832 | 42946523136 | 1 | Y |
To resolve this in Future, simply LIST Resources on those Exchange Servers and tick all Drives needing to be monitored. R: Drive in this instance.
Node Details Page or Manage Nodes > List Resource > Add R: Drive and save.
Useful Queries to troubleshoot:
AlertsHistoryView
SELECT TOP 2000 * FROM [dbo].[AlertHistoryView]
where RelatedNodeID = 251
order by timestamp desc
Volumes
SELECT TOP 5000 * FROM [dbo].[VolumeUsage_Detail]
where volumeID = 2617
order by Datetime desc
SELECT TOP 5000 * FROM [dbo].[VolumeUsage_Hourly]
where volumeID = 2617
order by Datetime desc
Events:
select top 5000 * from Events
where NetworkNode = 251
order by eventTime desc
EventID | EventTime | NetworkNode | EventType | Message |
1455259 | 2016-03-22T13:45: | 111 | 5000 | G: Drive: Warning Memory Utilisation (>90% <95%) - Windows 95 This alert reports the percentage of physical memory being used on Windows devices. |
1455253 | 2016-03-22T13:43: | 111 | 5000 | G: Drive:Warning Memory Utilisation (>90% <95%) - Windows 95 This alert reports the percentage of physical memory being used on Windows devices. |
1455252 | 2016-03-22T13:43: | 111 | 5000 | G: Drive:Warning Memory Utilisation (>90% <95%) - Windows 95 This alert reports the percentage of physical memory being used on Windows devices. |
1455143 | 2016-03-22T11:25: | 111 | 5000 | G: Drive:Warning Memory Utilisation (>90% <95%) - Windows 95 This alert reports the percentage of physical memory being used on Windows devices. |