[ Bottom of Page | Previous Page | Next Page | Contents | Index ]
There are five types of rules:
- Plain rule
- Used with incoming new events, or with previously received events to
be re-analyzed. Re-analysis of a previously received event is called a redo request.
Plain rules allow you the flexibility
to use any predicate or Prolog feature in its actions.
- Change rule
- Used with previously received events that have a request to change their
information. A request to change an event's information is called a change request. For change requests, the change rules
are checked before the change is actually made. This timing lets you develop
rules to take action depending on the old value of an attribute, the new value
of the attribute, and the origin of the change request. Change requests can
be generated by:
- An event console, for example, an administrator changes the status of
an event from OPEN to CLOSED
- Calling certain predicates within rules, for example, the place_change_request
predicate
- Receiving an event from an adapter with a value of CLOSED for the status
attribute
Change rules allow you the flexibility to use any predicate or Prolog
feature in its actions.
Change rules can only specify plain actions. Redo
actions and reception actions are considered errors when they are specified
in change rules. See Action types for additional
information.
- Timer rule
- Used when a previously set timer on an event expires. Timers can be
set on an event with the set_timer predicate in a rule. Sometimes you might
want to wait for a period of time so related events come in that help identify
the root cause of a problem, or perhaps you want to wait to ensure the event
condition lasts long enough to be a problem where action is needed. With
timer rules, you have the flexibility to use any predicate or Prolog feature
in its actions.
Timer rules can only specify plain actions. Redo actions
and reception actions are considered errors when they are specified in timer
rules. See Action types for additional information.
- Simple rule
- Used with incoming new events, or with a redo request. A simple rule
is not as flexible as a plain rule, for example, it contains predefined conditions
and actions, and you cannot use a predicate or any Prolog feature in its actions.
A simple rule does not do any correlation with other events in the event cache,
except for dropping duplicate events.
- Correlation rule
- Used with incoming new events, or with a redo request. A correlation
rule lets you establish a causal relationship between two event classes. One
event either causes the other to be generated, or one event causes the other
to be closed. With a correlation rule, you can propagate the value of the
status attribute from a cause event to an effect event. For example, when
closing a cause event, a linked effect event can be automatically closed,
also. Correlation rules are called compound rules in the rule builder dialogs.
[ Top of Page | Previous Page | Next Page | Contents | Index ]
