Configuring threshold values for disk partitions in OpManager
For the Servers, we discover Disk utilization using both WMI and SNMP. Also, we monitor the drive partitions that are available in those Servers.
The customers found this very effective except for those who had more Servers (where the threshold configuration by accessing each and every device is quite tedious).
To overcome this difficulty we came up with another function to update the threshold for drive partitions in bulk.
This can be achieved by going to Settings >> Configurations >> Quick configuration wizard >> Threshold Settings.
Under Performance Monitors, Select the Monitor type whether it is for Vmware datastore OR Partition details. Here Partition Details and Category as Servers.
The next page will list drive partitions of the Servers that are discovered.
Use the search (magnifying glass) icon to search & filter the specific drive partitions from all servers which will be listed. The drives can be selected for configuring the threshold.
Now the Configure Threshold page will pop up. Update the values, then Apply & Overwrite.
New to ADSelfService Plus?
Related Articles
Configuring response time and packet loss threshold values for a group of devices in OpManager
In this video you'll learn how to set response time and packet loss threshold values for a group of devices in OpManager Configuring thresholds on the devices monitored in OpManager
AD Monitors Shows N/A in OpManager
This problem could due to the following reasons: 1)WMI is not configured properly in OpManager (OpManager uses WMI credential to monitor AD servers). 2)Required Monitors are not associated to the device in OpManager. 3)WMI might not be responding to ...Configuring a non-admin user for WMI monitoring (domain level)
For non-admin users to perform WMI monitoring in OpManager, the user profiles need to be configured accordingly in your network. This can be done: On a device level (configuring individual devices) - Link to KB On a domain level (configuring the ...MSSQL Monitors not working - Shows N/A in OpManager
This problem could due to the following reasons: 1)WMI is not configured properly in OpManager (OpManager uses WMI credential to monitor MSSQL servers). 2)Required Monitors are not associated to the device in OpManager. 3)WMI might not be responding ...