Page tree

Skip to end of metadata
Go to start of metadata

Correlate rules build a cause-effect relationship between two events, where one occur as a result of the other. Correlate rules execute whenever a cause or an effect event is received. The relationship between correlated events can be broken.

The relationship between correlated rules can be broken by using the unset_cause primitive. For more information about the unset_cause primitive, see Correlate rule primitives.

In versions of Infrastructure Management earlier than 9.0, the rule that established a cause-effect relationship was not tied to the event relationships it created. According to a correlate rule, an event had a maximum of one cause. If two correlate rules (or correlate policies) established different cause for the same event, the effects were undefined.

In this version of Infrastructure Management, an event can have one cause per rule or correlate policy. The cell maintains a link between each correlate rule/correlate policy and instances of the event relationship.

The advantages of this change are better performances and a more sophisticated display of these relationships.

You can still use the rules written for earlier versions of Infrastructure Management. Event relationships established by abstract or correlate rules in earlier versions have been migrated to two categories of relationships: abstract_legacy and correlate_legacy based on the now obsolete mc_abstracted, mc_abstraction, and mc_cause, mc_effects slots.

These relationships will be displayed in the Operations Console. However, if you modify these old events, the rules will not be triggered.