Automatic Corrective Actions

Field Description

Field Name

Execution Type. Specifies when the action should be executed. Available options are:

• Rise. Execute each time an alert instance is created.
• Activation. Execute upon alert trigger activation for a certain context. Very similar to Rise, except for that activation will not happen for event triggers that have no correlated events.
• Deactivation. Execute upon alert trigger deactivation for a certain context.
• Escalation. Execute once the alert is escalated.
• Deescalation. Execute once the alert is de-escalated.
• Acknowledgment. Execute once any alert instance (instance of an alert event) is acknowledged.

executionType

Corrective actions initiated upon Acknowledgment will only run if one of the pending instances was acknowledged.

Context Mask. Action will be executed from every context matching this mask.

mask

Action. Name of the action to be executed.

action

Parameters. This list incudes parameters of two types: action-specific execution parameters and pre-defined input for different UI Procedures like Confirmation, Edit Data etc. Pre-defined input is required to substitute user input when alert executes action in non-interactive mode. For example, if an automatic corrective action requires confirmation (i.e. asks user something like "Delete query?" and allows to click OK or Cancel), this field will contain a "Delete query?" parameter with two possible choices: "OK" and "Cancel".

input

Condition. An expression that is evaluated before corrective action execution. If the expression returns false corrective action is skipped.

condition

Default Context

Context of the alert.

Default Data Table

Data of alert event.

Default Row

0

Environment Variables

Standard variables only.

Run From Source Context. If this flag is checked, corrective action will be launched from the context that the alert came from.

The Context Mask parameter is ignored if Run From Source Context is on. However, it's necessary to select a Context Mask that will match one or all possible alert source contexts first, since this will allow proper selection of an Action and its Parameters.

runFromSource

Example: If an alert monitors memory usage of an application that has memory leaks, selecting Restart corrective action and enabling Run From Source Context will restart the application on the server that has originated the alert. Same applications on other servers will not be touched.