AggreGate Server is capable of running actions when an alert is raised. These are called "corrective actions" because they're intended to correct the problem automatically or by interacting with humans.
|
Corrective actions may be also used to send non-standard notifications. For example, corrective action may launch an external application to send message to a pager or beeper (check details here). Another examples would be sending Unix syslog message or Simple Network Management protocol (SNMP) trap using special actions included into AggreGate Network Management extensions. |
Actions may be run in interactive or non-interactive (headless) mode. In non-interactive mode, all action input is pre-defined and action output is sent to the server log or written to event history. This mode is also used by the scheduler. In interactive mode, the action interacts with the alert owner by using UI Procedures. He must be logged in to an AggreGate Server User Interface (e.g. AggreGate Client) to allow interactive actions execution. See the action execution modes section for details.
Non-interactive execution is controlled by the Automatic Corrective Actions property. This property lets you configure multiple actions to run on alert, and has several parameters: Every action will be launched from every context matching the Context Mask parameter. Action name is defined by the Action parameter. Parameters is the list of action-specific parameters (this might be confusing, but keep in mind that Parameters here is, itself, a parameter. Get it?). These parameters are used to substitute user input when the alert processing engine executes an action in non-interactive mode. For example, if a given action requires confirmation (i.e. asks user something like "Delete query?" and lets the user click OK or Cancel), this field will contain a Delete query? parameter with two possible choices: OK or Cancel.
Interactively executed actions are listed in a table called Interactive Corrective Actions. Every action has two parameters: Context Mask and Action, which work just like in non-interactive execution (see above). There is no Parameters field in this list, since all input for interactive actions is provided by a human user.