Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Volume capacity alert firing on multiple servers for a single network drive

Volume capacity alert firing on multiple servers for a single network drive

Created by Matthew Lamb, last modified by Rodim Suarez on Jun 26, 2016

Views: 19 Votes: 0 Revisions: 4



This article goes over on how to work through an issue where a single network drive being used by multiple, monitored servers is being alerted on multiple times.


All NPM versions


The reason this issue can occur is because of the nature in which nodes themselves are monitored for their volume information. 


As an example, you have drive A being used by servers 1, 2, 3 and 4. All 4 of those servers are mapped to that drive and all of those servers are being polled for volume information in NPM\SAM.

Now, when it comes to that volume, it will not be stored as a unique, single, global entity. The reason for this is that the drive information is gathered via the nodes instead, each with its own node id. When server 1 is polled, it records drive A as its own unique volume ID underneath it. When server 2 is polled, the same occurs, etc. down the line.

So when you set an alert to fire when drive A reaches 90%, it fires multiples because there actually IS multiples in the database for that drive. That drive in reality will be labeled under a unique volume id entity as volume 1A, then 2A, then 3A, then 4A. Each of those volume entities in the database will have the statistical data gathered from each of those servers for that volume based on it's perspective, so each will be unique.

So the actual problem here isn't that the alert is working incorrectly, it is just too broadly defined for what you are looking for. What you will need to do with the trigger information is define it specifically to either a single node to alert on or to a single volume ID for that drive to alert on. If you set the trigger for just the volume, then you'll have multiple alerts because there are multiple instances of that volume underneath all of it's polled nodes.


You will need to define the alert to trigger off just a single instance of that volume on one of the servers. Since all the servers should have the same statistical information for that volume, any of them as a single alerting point should work. It's possible to define this further via SQL or SWQL query as well.


Last modified
17:13, 26 Jun 2016