options for running scripts in CDM probe when threshold is breached

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

The CDM probe 7.21 has the following in the release notes:

• Added support to execute scripts when the memory, disk, or CPU threshold value is breached.

The release notes for 7.22 additionally have the following:

• Added support to execute scripts for specific alarms/metrics when the threshold value is breached.

 

How is this configured?

 

Environment

DX UIM - Any Version
CDM Probe - 7.21 and higher

Resolution

There are two options for script execution which are accessible via different methods:

1. Execute a script when any threshold is breached (configurable in either Infrastructure Manager or Admin Console) - supported by CDM 7.21 and higher
2. Execute a script when a specific threshold is breached (configurable only in Infrastructure Manager)  - supported by CDM 7.22 and higher

 

Method 1 - execute a script when any threshold is breached

For CDM 7.21 and higher, you may configure the probe to execute a script when any threshold of any kind is breached.

In Admin Console this is located at the top of the configuration tree and looks like this:

In Infrastructure Manager, this option is located in the Setup tab, in the "Control Properties" sub-tab.

This will cause the given script to execute whenever any threshold is breached.  It is not possible to determine within the script which threshold was breached when using this option.

 

Method 2 - execute a script when a specific threshold is breached

Starting in CDM 7.22 the option exists to run a specific script when a specific threshold is breached.

This is only accessible in the Infrastructure Manager GUI for CDM and is located under the 'Setup' tab, "Message definitions" sub-tab.

In this tab, locate the message that corresponds with the threshold you are interested in - for example, the "Major" threshold for CPU Usage as seen here corresponds to "CPUErrorProcesses":

 

Double-click on the message in question and a new window will open up, allowing you to edit the message and its properties:

 

Here you can specify an individual script to run when this threshold is breached.

There are no variables available to determine which threshold was breached;  our recommendation is to use a separate "instance" of each script per threshold, with some logging added to the script itself that specifies which threshold it belongs to.