8.9.3.1 Creating an Incident Rule

An incident rule specifies condition details that trigger a resource broker policy. The condition can be complex and made up of criteria combination that represents the event characters (for example, the event type, severity, category, and etc.). By defining incident rules, you can specify when one of the following conditions is met, the deployment policies are evaluated:

• The CPU utilization of a host reaches 85%
• The average execution time of certain Tuxedo service exceeds 500 microseconds
• Some Tuxedo machines are down, etc.

An incident rule can contain any metrics provided by any monitored target. To allow the incident rule to be evaluated on specific targets, create the Enterprise Manager Group on the targets and refer to this group in the rule set.

The following steps are given as an example to introduce how to define a CPU metric even type. Before creating a policy, you need to create incident rules.

1. From the Enterprise Manager console home page, click Setup-> Incidents -> Incident Rules
2. On the Incident Rules page, click Create Rule Set...
3. Enter a rule name, and choose Specific targets on the Targets tab at the bottom of the page.
4. Add your predefined Enterprise Manager Group(s) which contain(s) the target events under consideration.

   Note:

   Selecting specific groups in this step is important, otherwise all the events of same type on any target implements the incident rule.
5. Choose the Rules tab. Click Create to create a incident rule.
6. Click Continue in the pop-up window to define an event-type incident rule.
7. In the page that appears, select Type. Choose Metric Alert in the list.
8. Choose Specific events of type Metric Alert

   A Metric Alert panel appears.

9. Click Add to designate a specific Metric Alert event.
10. In the Select Specific Metric Alert page, define an incident rule carried out when the CPU utilization of one host reaches the Warning threshold, as shown in figure below:

    Define a CPU Metric Event- Example

    Figure 8-7 Define a CPU Metric Event- Example

    
    

    

    
    
11. Click OK.

    The newly-created event appears in the Metric Alert panel.

12. Click Next to proceed to the Add Actions step page.
13. In the Advanced Notifications panel, check the predefined notification named Tuxedo Event Connector (PL/SQL Procedure) .

    This means when the incident is produced, Tuxedo Event Connection is notified.

14. Click Continue in the upper right corner to complete the definition. Click Next.
15. Enter a name in the Specify Name and Description page. Click Next, and then Continue to finish the configuration.

    On the All Enterprise Rules page, you can find the incident rule is added under the Tuxedo Incident Rules rule set with “active” status.

16. Return to the Edit Rule Set page. Click Save to activate the defined incident rule.

On the All Enterprise Rules page, you can find the incident rule is added under the Tuxedo Incident Rules rule set with “active” status.