Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > Server & Application Monitor (SAM) > Server & Application Monitor Getting Started Guide > Reduce alerting noise > Alerts with device-specific thresholds

Alerts with device-specific thresholds

Table of contents
No headers
Created by Chris.Moyer, last modified by Anthony.Rinaldi on Aug 23, 2016

Views: 345 Votes: 1 Revisions: 6

You can set different alert thresholds per device, interface, or other monitored element. For example, it is acceptable to you if most of your nodes reach a 90% threshold for CPU load, but you want a few nodes to alert when they reach a 70% threshold. You can set CPU thresholds locally on a node, and then create a generic alert that notifies you when a threshold has been reached.

  1. Begin by creating the actual trigger condition with a double value comparison.
    1. Click the plus sign.
    2. Select Add Double Value Comparison.

      The trigger condition fields expand, and you can enter a double value comparison trigger.

      File:Success_Center/New_Articles/NPM-CHM-Import/Onboarding-Guide-CHM/0F0/060/Device_Thresholds1.png

  2. Include the threshold in the trigger condition.

    An alert will be triggered when the threshold value is reached.

    File:Success_Center/New_Articles/NPM-CHM-Import/Onboarding-Guide-CHM/0F0/060/Device_Thresholds2.png

 
Last modified
15:55, 23 Aug 2016

Tags

Classifications

Public