Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Custom node thresholds not being used for coloured status

Custom node thresholds not being used for coloured status

Created by Tiarnan Stacke, last modified by Gary O'Donovan on Oct 17, 2016

Views: 931 Votes: 1 Revisions: 4

Overview

Custom node thresholds are not being used for coloured status. For example, if custom thresholds are applied on a node for memory utilization, it does not affect the Warning/Critical colour of the memory utilization in the charts or other resources. Instead, they will go Warning/Critical based on the Global Thesholds.
 

Environment

  • NPM 11.5 and earlier
  • SAM 6.2.3 and earlier

Cause 

This is a product bug.

Resolution

No Resolution at present, but issue will be addressed in a future release.

 

Last modified

Tags

Classifications

Public