Rule-based Event Compression

Rule-based Event Compression is an older method of automatically compressing multiple events into a single incident.

Note:

Oracle recommends using the newer Event Compression Policies method as it is easier to configure. You only need to configure it once and it will apply to all rules, as opposed to individual rules.

Some situations where it is beneficial to deal with multiple events as a single incident are:

  • You want automatic consolidation of all Tablespace Used (%) alerts across all tablespaces for a specific database into a single incident.

  • You want automatic consolidation of all Metric Collection Errors for a target into a single incident.

  • You want automatic consolidation of all SOA composite Target Down events within a WebLogic Domain into a single incident.

For convenience, Enterprise Manager provides out-of-box rules that automatically compress related events into single incidents. These rules address some of the most common conditions where event grouping could be helpful.

  • Target down for RAC database instances.

  • Metric collection errors for a target.

  • Configuration standard violations for a rule on a target.

Creating an Incident Compression Rule Set

The following example shows you how to create an incident rule set that generates a single incident (compressed), and notifies an administrator of via email that a compressed incident has been generated.   

  1. Click Setup > Incidents > Incident Rules.
    Incident rule menu

  2. Click Create Rule Set.
    Rule set menu selection.

  3. Enter the name of the Rule Set and select the target the rule applies to. In this example, a Database Instance target is selected.
    Edit rule set.

  4. Scroll down to the Rules section and click Create.
    Click Create.

  5. In the Select Type of Rule to Create popup window, leave the default (Incoming events and updates to events) selected and click Continue.
    Rule type selection.

  6. Select Target Availability from the Type drop down menu and select Specific events of type Target Availability. Click Add.
    Edit rule.

  7.  Check the “Down” checkbox and click OK.
    Availability states.

  8. Click Next.
    Select event type.

  9.  Click Add to add Conditional Actions.
    Add conditional action.

  10.  Select the conditions for compressing the events and click Continue. In this example we are compressing events from targets on the same host.
    Add conditional actions.

  11. Click OK in the popup window.
    warning

  12. Click Next.
    Incident rule

  13. Provide a name for the rule and click Next.
    rule name

  14. Click Continue to add the rule.
    Add rule.

    Next, you will create a new rule to notify an administrator for the compressed incident.

  15. Click Create to create a new rule to configure email notification.
    Email notification rule.

  16. Select Newly created incidents or updates to incidents and click Continue.
    Select type of rule.

  17. Select Specific incidents. 

    1. Select the checkbox for Rules that created the incidents and select the rule that you just created.

    2. Select the checkbox for Status and select New.

    3. Click Next.


    Select specific incidents.

  18. Click Add to add a Conditional Action.
    Add conditional action.

  19. Populate Conditional Actions as shown in the screen shot below. Change the notified user according to your requirement.
    Add action.

  20. Click Next.
    Affirm add action.

  21. Enter a name for the rule and click Next.
    Define rule name.

  22. Click Continue.
    Affirm name and description.

  23. Click Save to save the rule set.
    Save the rule set.

  24. Highlight the rule set and click Reorder Rule Sets.
    Reorder rule set.

  25. Move the rule set to the top and click OK.
    Confirm rule set order.

    Once the new rule set is moved to the top of the list, it will be evaluated first by the rules engine.