Type
  • Best Practice
Description
  • This article explains how to set agent thresholds for Sentry Software's KMs through a CMA policy.
Additional Keywords
  • Events, Agent Threshold

Related Topics

Knowledge Base

How to Manually Set Agent Thresholds in a CMA Policy

KB1223 - Jun 15, 2018

Introduction

By default, PATROL events are not generated when thresholds are breached if Sentry Software's KMs have been configured through CMA. To be able to use the Sentry Software KMs' macro variables and events, you will have to set agent thresholds.

To illustrate how to set agent thresholds, the following use case will be described in this article:

  1. We will configure Monitoring Studio to run the command cat /usr/local/monitor/servicestatus.log to obtain the status of the SNMPD_SVC service.
  2. Then, we will extract the numeric value contained in the 3rd column of the log file, which uses pipes (|) as column separator:

    HTTPD_SVC|NORMAL|0|OK
    SNMPD_SVC|ALARM|2|BAD
    
    Note: The Flat File monitor could also be used for this use case.
  3. Finally, we will set an Agent Threshold on the instance of this Numeric Value Extraction to have the following event to be triggered when SNMP is down:

inline

Procedure

To configure an Agent Threshold on a specific instance:

  1. Create a monitoring policy for Monitoring Studio
  2. Configure a Monitor Group:

    • In the Add Configuration Panel, click Add to open the Monitor Groups panel
    • Specify the Host Settings:

      Configuring a Monitor Group

      • Hostname: Enter the name (or IP address or Fully Qualified Domain Name) of the host on which the technology you wish to monitor is running
      • System Type: Select the type of the operating system that is running on the host that will be monitored (Windows, UNIX/Linux, or Other). Select Other for any host that will not behave as a regular Linux or UNIX system would.
      • System Username: Enter the username that will be used by Monitors relying on System Credentials to collect data from the targeted host.
      • System Password: Enter the password for the username provided above, that will be used by Monitors relying on System Credentials to collect data from the targeted host.
      • Create a Device in the Console: Select this option if you wish Monitoring Studio to create an instance of the device in TrueSight Operations Management. All associated Monitors and their events and attributes will be attached to this new device in TrueSight Operations Management. If this option is not selected, they will be attached to the device matching the PATROL Agent host.
  3. Configure the Command Lines monitor:

    • Scroll down to the Command Lines section and click Add to configure the command line to execute
    • In the Command Line Settings field, enter cat /usr/local/monitor/servicestatus.log
    • Enter the Monitor Settings Internal ID and Display Name (in our example servicestatuslog and Service Status Log)
    • Click OK.

      Configuring the execution of a command line

  4. Configure the Numeric Extractions monitor:

    • Scroll down to the Numeric Extractions section and click Add
    • From the Extract Numeric Values From list, select Lines Matching the Regular Expression Below and enter the name of the service. In our example, SNMPD_SVC
    • From the Numeric Values are Located list, select In the Column Number Specified Below and enter 3
    • From the Expected Format list, select 100000
    • Select Pipe (|) as the column separator.

      Configuring the extraction of a numeric value

  5. Configure Alert Actions for the Numeric Value Extraction:

    • Scroll down to the Monitor Settings section
    • In the Internal ID field, enter SNMPD_NumExtract
    • In the Display Name field, enter Numeric Value Extraction
    • Check the Upon Thresholds Breach, Trigger an Event and Upon Thresholds Breach, Annotate the Graph boxes and indicate the Event and Annotation context (in our example: The SNMP service is down on %{SEN_HOST_NAME})

      Configuring alert actions

  6. Click OK for all opened panels

  7. Click the Agent Threshold tab and click Add Agent Threshold

    Configuring agent threshold

    • From the Monitoring Solution list, select Monitoring Studio
    • Select the relevant version
    • From the Monitor Type list, select Studio Number Extract
    • From the Scope list, select Instance and enter the Instance SID. The Instance SID can be found in the TrueSight Infrastructure Management console by placing the cursor on the required instance:

      inline

    • In the Threshold 1 section, check the Enable box and enter 2 in the Min and Max fields

    • From the Select Event Severity list, select Critical
    • From the Trigger an Event, select Immediately on threshold violation
    • Click OK
  8. Click Save.

To verify that the agent thresholds have been correctly applied, run the following PSL statement through the "Query PATROL Agent" menu:

print(get_ranges("/SEN_MS_NUMBER/<Group ID>@<Host ID>:CommandLine:<Command-line ID>:Number:<Numeric value Extraction ID>/Value")."\n");

where:

  • <Group ID> is the Internal ID as entered when configuring the Monitor Group Settings
  • <Host ID> is the hostname
  • <Command-line ID> is the Internal ID as entered when configuring the Internal ID of the Command Line Monitor
  • <Numeric value Extraction ID> is the Internal ID as entered when configuring the Numeric Value Extraction Monitor

In our example: print(get_ranges("/SEN_MS_NUMBER/SNMPD_Status@babbage:CommandLine:servicestatuslog:Number:SNMPD_NumExtract/Value")."\n");

If agent thresholds are correctly applied, you should obtain the following result:

0 0 0 0 0 0
1 2 2 0 0 0
0 0 0 0 0 0