Correlation Rules

Use the Correlation Rules manager to view, define, and apply correlation rules. Correlation rules associate selected configuration item types with defined indicator states to trigger a correlation process. The correlation process results in the highlighting of one or more configuration items as causes.

Correlation rules require a combination of symptoms and causes. Both symptoms and causes are defined by selecting configuration item types. Each configuration item type (such as a DB2 database) that you specify as a potential symptom requires one or more indicators (for example, Run State, or Availability) to be defined for it. Each indicator must have a state (for example, up, down, or offline). Configuration item types you choose as causes also require an indicator and a state.

For example, the information in the following table defines a simple correlation rule for a database instance. OMi displays cause events in the Event Browser and the symptom events in the Related Events tab of the Message Details pane.

Rule Type

CI Type

Event Type Indicator

Event Type Indicator State

Symptom

DB2

Network Availability

Offline

Symptom

DB2

Buffer Hit Ratio

Low

Symptom

Process

Run state

Down

Cause

DB Table Space

Buffer Performance

Slow