What a Rule is
A Rule is basically a two-part conditional statement: when the conditions of the first part of the statement are met, the actions of the second part of the statement are performed. The two parts of the statement are called
- selection criteria
- action specifications
Selection criteria
Selection criteria are user-specified event attributes the Rule uses to recognize an event that will be automated.
When you create a Rule, you must choose specific attributes of the event that the Rule will try to match to incoming events. When the specified selection criteria match that of an incoming event, the Rule fires and the automation action will be taken (see Action specifications below).
Each event type has its own version of a selection criteria panel, which contains only the applicable attributes for that event. For more information about selection criteria, refer to Step-1-Using-Selection-Criteria-fields.
Action specifications
The second part of a Rule is a set of user-specified automation actions (also called action specifications).
When a Rule’s selection criteria matches an incoming event and the Rule fires, the user-specified automation actions are performed. This action is also called handling the event.
Some examples of automation actions are suppressing a message from appearing on the console or issuing an ALERT that notifies an operator of an exceptional situation that requires operator intervention.
Each event type has its own versions the action specification panels that contain all the applicable actions that a Rule can perform for the event. For more information about action specifications, refer to Step-3-Specifying-a-Rule-s-actions-with-the-Action-Specification-fields.
In summary, a Rule screens incoming events for matches to user-specified selection criteria and, when the attributes of an event match the selection criteria, the Rule fires and performs the user-specified automation actions.