Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Overriding Global thresholds for Memory Used

Overriding Global thresholds for Memory Used

Updated December 18, 2017


When you adjust the thresholds for Memory Used for Hosts in Virtualization tabs in the Top 10 VMware Hosts, the thresholds don't stay set:


Top 10 Vmware Hosts by Percent Memory Used 1.PNG


The bar on the right side is based on the Global Threshold values.


The Status icon on the left side is based on the overridden threshold values for Warning and Critical. The colors above don't match because the overridden thresholds are set to higher values for Warning and Critical.


The Top 10 xx resource uses only general thresholds and does not consider overridden values for specific hosts. It makes sense if you consider the resource displays hosts in a data center and it orders it by memory percent usage.


  • NPM 12.1


When you enable Override Global Orion Threshold for Memory Usage, this doesn't work for under Virtualization - Hosts. It will reset.


For Cluster it will work.

Overriding Global threshold for a Host 1.PNG


These follow the Global Memory threshold values set in:

Global Percent Mmeory Used settings 1.PNG



Adjusting general thresholds should fix the issue.

Wait until the thresholds cache expires, or open the page in a new session/incognito mode/different browser (or reset the IIS).





Last modified