Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

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: 916 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