Event Monitor Logic

 

Updated: May 13, 2016

Applies To: System Center 2012 R2 Operations Manager, System Center 2012 - Operations Manager, System Center 2012 SP1 - Operations Manager

Event monitors in System Center 2012 – Operations Manager use one of the event data sources to identify a particular event that indicates an issue. As soon as the specific data source that holds the required information is identified, the logic used to determine different health states must be determined. In addition to the logic that indicates whether an error condition has occurred, additional logic must be defined to determine when the state should be changed back to a healthy condition.

The different kinds of logic that can be used to detect an error condition by using events are listed in the following table. See the individual topic for each condition for details on how its logic is implemented. As noted in the table, some logic can only be used with Windows events.

Logic

Data Sources

Description

Simple Event

All

Detects an error state from the occurrence of a single event. There is no individual topic for this logic.

Repeating Events

All

Detects an error state from one or more occurrences of a particular event in a specified time window.

Correlated Events

Windows Events

Detects an error state from the occurrence of two events in a specified time window.

Correlated Missing Events

Windows Events

Detects an error state from an expected event not being detected in a particular time window after the occurrence of another event.

Missing Events

Windows Events

Detects an error state from an expected event not being detected in a particular time window.