Missing Recurrence Rules

Events are sometimes regularly generated to inform that no problem has occurred, for example "alive" events indicate that a system is running. As soon as the expected regular event is not received, it can be assumed that there is a problem, for example, if a system stops reporting “alive” events every 10 minutes, it has probably stopped running.

Configuring a missing recurrence rule requires a filter to select the events to consider, for example, to select events with "node alive" in the title. Certain attributes must be the same to be regarded as originating from the same source, for example, the node, CI and source CI must be the same. The time allowable interval before an expected event is considered to be missing must be specified, for example, a maximum of 10 minutes in our example.

It may be considered advantageous to discard recurring events to reduce the number of unnecessary events being sent to the Event Browser.

When the expected event is not received within the specified time period, is it necessary to inform the operator that action is necessary. A new event can be automatically generated. All matching events can be related to the new event as symptoms.

Tasks

UI Descriptions