This page describes the standard events published by the agent that reveal a state change. It describes the circumstances leading to event publication and other details. The following table lists the events and to what class they belong.
Standard events that reveal a state change
Standard event | Event class |
---|---|
1 | Computer state event |
2 | Computer state event |
3 | Computer state event |
9 | Parameter alert event |
10 | Recovery action event |
11 | Parameter alert event |
12 | Recovery action event |
39 | Parameter alert event |
UpdAppState | Application state event |
UpdInstState | Instance state event |
UpdMachineState | Computer state event |
UpdParState | Parameter state event |
WorstApp | Application state event |
Following are the event classes for standard events published by PATROL Agent:
Every time the state of an application instance (see Instance state event) changes, the parent application state is also checked. As a result the following Events are published:
The UpdAppState Event is published every time the worst instance of the computer is calculated:
The following table provides description, default, severity, and configuration information for the UpdAppState and WorstApp Events:
UpdAppState | WorstApp | |
---|---|---|
Description | Update state of application %s. | Worst instance of application '%s' is '%s'. |
Default SNMP setting | No trap | |
Default storage | PEM circular file | |
Severity | High (4) if new state is ALARM Medium (3) if new state is WARN Low (2) if it is another state change Very low (1) if no state change occurred in the application | |
Configuration | Setting AR_ALLOWSENDPARAMONLY to yes in patrol.conf will disable publishing of these events. By default it is set to no. |
The computer state changes in the following circumstances:
As a result of a computer state change, the UpdMachineState Event is published when the new computer state is different from the previous one. Event argument #2 indicates the reason:
If the computer state did not change, the following events are published:
The following table provides description, default, severity, and configuration information for the UpdMachineState, 1, 2, and 3 Events:
UpdMachineState | 1 | 2 | 3 | |
---|---|---|---|---|
Description | Update status of host: %s %s. | Current state of '%s' is %s. | Current state of '%s' is inherited from application '%s'. | Current state of '%s' is inherited from instance '%s' of application '%s'. |
Default SNMP setting | No trap | |||
Default storage | PEM circular file | |||
Severity | Low (2) | |||
Configuration | Setting AR_ALLOWSENDPARAMONLY to yes in patrol.conf does not affect the events. By default it is set to no. |
The UpdInstState Event is published as follows:
The following table provides description, default, severity, and configuration information for the UpdInstState Event:
Parameter | UpdInstState |
---|---|
Description | Update status for instance %s.Reason:%s |
Default SNMP setting | No trap |
Default storage | PEM circular file |
Severity | High (4) if new state is ALARM |
Configuration | Setting AR_ALLOWSENDPARAMONLY to yes in patrol.conf will disable publishing of this event. By default it is set to no. |
Parameter Alert Events are those events related to parameter range and border definitions. As an example, let's assume the following ranges:
The table below shows which event is generated when a parameter value changes from one range to another.
Parameter | Normal | Alarm #1 | Alarm #2 | Out-of-Range |
---|---|---|---|---|
Normal | NA | 11 | 11 | 39 |
Alarm #1 | 9 | NA | 11 | 39 |
Alarm #2 | 9 | 11 | NA | 39 |
Out-of-Range | 9 | 11 | 11 | NA |
The following sequence of values will validate all state transitions. Note that the out-of-range state or alert state must not affect the state transitions. Setting out-of-range state and alert states to (OK, OK, OK) or (WARN, WARN, WARN) will produce the same state transitions.
The following table provides description, default, severity, and configuration information for Events 9, 11, and 39:
9 | 11 | 39 | |
---|---|---|---|
Description | Alert on '%s' from %s parameter '%s' cancelled; exception no longer exists. | %s of %s parameter '%s' triggered on '%s'. %d <= %f <= %d | %s of %s parameter '%s' triggered on '%s'. %f %s %d |
Default SNMP setting | Trap | Trap | No trap |
Default storage | PEM circular file | ||
Severity | Medium (3) | High (4) | Medium (3) |
Configuration | Setting AR_ALLOWSENDPARAMONLY to yes in patrol.conf does not affect the events. By default it is set to no. |
UpdParState Event is published when a parameter satisfies the following conditions:
The following table provides description, default, severity, and configuration information for the UpdParState Event:
Parameters | UpdParState |
---|---|
Description | Update status of parameter %s: new value %s. |
Default SNMP setting | No trap |
Default storage | PEM circular file |
Severity | High (4) if new state is ALARM |
Configuration | Setting AR_ALLOWSENDPARAMONLY to yes in patrol.conf does not affect the event. By default it is set to no. |
Event 10 is published when a recovery action runs. Event 12 is published when all recovery actions run, but failed to correct the state of a parameter.
The following table provides description, default, severity, and configuration information for Events 10 and 12:
10 | 12 | |
---|---|---|
Description | All recovery actions have been run. | Recovery action run in response to the %s alert generated by %s parameter '%s' of '%s'.%s. |
Default SNMP setting | No trap | |
Default storage | PEM circular file | |
Severity | Medium (3) | |
Configuration | Setting AR_ALLOWSENDPARAMONLY to yes in patrol.conf does not affect the events. By default it is set to no. |