Managing Thresholds: the Event Management Thresholds Mechanism

How to manage Event Management thresholds in Hardware Sentry KM for PATROL.

Related Topics

Description

The Event Management thresholds mechanism relies on the Event Management KM to set alert thresholds. In order for this mechanism to work properly, the Event Management KM should be preloaded on the PATROL Agent (the AS_EVENTSPRING.km and AS_EVENTSPRING_ALL_COMPUTERS.km must be included in the /AgentSetup/preloadedKMs configuration variable).

Thresholds can be applied to a single instance of a class (instance-specific) or to all instances of a single class (such thresholds are called “global” and are referred to as “ANYINST thresholds”). When both types of thresholds are applied to a parameter, the single instance thresholds take precedence over the ANYINST thresholds.

Threshold settings are stored in the agent’s configuration under the /AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS folder.

Applying Thresholds to a Single Instance

Thresholds apply to the instance specified by the configuration variable path.

Configuration Variable Path

Thresholds are set in the following configuration variable:

/AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/<class  name>/<object ID>/<parameter name> 

Example

  /AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/MS_HW_FAN/MS_HW_DellOpenManagehdflocalhost_11/Speed 

This variable contains the thresholds that apply to the “Speed” parameter of the “MS_HW_DellOpenManagehdflocalhost_11” PATROL instance of the MS_HW_FAN class.

Variable Format

The format of the variable is:

# Example Content definition
1 1 Parameter activation (0 = inactive, 1 = active)
2 0 Border activation (0 = inactive, 1 = active)
3 0 Border minimum threshold
4 0 Border maximum threshold
5 0 Border trigger type (immediately, after n times, after all recovery actions have failed)
6 0 Border Max number of occurences (n times)
7 0 Border alarm type
8 1 Alarm 1 activation (0 = inactive, 1 = active)
9 1 Alarm 1 minimum threshold
10 1 Alarm 1 maximum threshold
11 1 Alarm 1 trigger type (immediately, after n times, after all recovery actions have failed)
12 1 Alarm 1 Max number of occurences (n times)
13 1 Alarm 1 alarm type
14 1 Alarm 2 activation (0 = inactive, 1 = active)
15 2 Alarm 2 minimum threshold
16 2 Alarm 2 maximum threshold
17 1 Alarm 2 trigger type (immediately, after n times, after all recovery actions have failed)
18 1 Alarm 2 Max number of occurences (n times)
19 2 Alarm 2 alarm type

Example

Thresholds that immediately trigger a warning if value is 1 and an alarm if value is 2.

  1,0 0 0 0 0 0,1 1 1  1 1 1,1 2 2 1 1 2 

Applying Thresholds to Multiple Instances of a Parameter

Applying Thresholds to all Instances of a Parameter

Configuration Variable Path

Thresholds are set in the following configuration variable:

/AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/<class>/__ANYINST__/<parameter> 

Example

  /___tuning___/MS_HW_FAN/ALL_INSTANCES/Speed 

This variable contains the thresholds that apply to all instances of the “Speed” parameter of the MS_HW_FAN class.

Variable Format

The content of the variable is identical to the content of the single instance thresholds variable.

Applying Thresholds to Instances of a Parameter Matching a Regular Expression

Wildcards can be used in the instance name to apply thresholds on all the instances that match the specified regular expression.
The syntax is:

/AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/<class>/<instance  information>{re:*}/<parameter> 

Example

  /AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/MS_HW_FAN/MS_HW_DellOpenManagehdflocalhost_{re:*}/Status 

The thresholds will be applied to all “Status” parameters of the MS_HW_FAN class on the localhost discovered by the Dell OpenManage connector.

Important Note: Alert thresholds set in the agent’s configuration are not taken into account on the fly. It is necessary to set the /AS/EVENTSPRING/PARAM_SETTINGS/STATUSFLAGS/paramSettingsStatusFlag configuration variable to ‘6’ and wait for 40 seconds.