Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Server & Application Monitor (SAM) > SAM Documentation > SAM 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_ret, last modified by Anthony.Rinaldi_ret on Aug 23, 2016

Views: 978 Votes: 3 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

Tags

Classifications

Public
/*]]>*/