Rule Actions
For each rule, Enterprise Manager allows you to define specific actions.
Some examples of the types of actions that a rule set can perform are:
-
Create an incident based on an event.
-
Perform notification actions such as sending an email or generating a helpdesk ticket.
-
Perform actions to manage incident workflow notification via email/PL/SQL methods/ SNMP traps. For example, if a target down event occurs, create an incident and email administrator Joe about the incident. If the incident is still open after two days, set the escalation level to one and email Joe's manager.
The following table summarizes available actions for each rule application.
Table 5-6 Available Rule Actions
Action | Event | Incident | Problem |
---|---|---|---|
|
Yes |
Yes |
Yes |
Page |
Yes |
Yes |
Yes |
Advanced Notifications |
|||
Send SNMP Trap |
Yes |
No |
No |
Run OS Command |
Yes |
Yes |
Yes |
Run PL/SQL Procedure |
Yes |
Yes |
Yes |
Create an Incident |
Yes |
No |
No |
Set Workflow Attributes |
Yes Note: Within an event rule, the workflow attributes of the associated incident can also be updated. |
Yes |
Yes |
Create a Helpdesk Ticket |
Yes Note: Action performed indirectly by first creating an incident and then creating a ticket for the incident. |
Yes |
No |
Note:
you can test rule actions against targets without actually performing the actions using Enterprise Manager's event rule simulation feature. For more information, see "Testing Rule Sets".