Algorithm (DependencyMonitor)

Article
05/16/2012

Applies To: Operations Manager 2007 R2, System Center Operations Manager 2007

Defines the algorithm to use for determining health state.

Schema Hierarchy

ManagementPack
  Monitoring
    Monitors
      DependencyMonitor
        Algorithm (DependencyMonitor)

Syntax

<Algorithm>BestOf/WorstOf/Percentage</Algorithm>

Attributes and Elements

The following sections describe attributes, child elements, and the parent element of the Algorithm element.

Attributes

None.

Child Elements

None.

Parent Elements

Element	Description
AggregateMonitor	Defines a state machine whose health state is determined by an algorithmic analysis of its children.
DependencyMonitor	Defines a state machine whose health state is determined by an algorithmic analysis of a hosting or containment relationship’s target instances.

Text Value

The algorithm for determining the health state of a dependency monitor can be one of the following:

BestOf
WorstOf
Percentage

Remarks

The BestOf algorithm indicates that the monitor will reflect the state of its “most healthy” child monitor. For example, if one child is at a warning state and the other is unhealthy, the reflected state will be a warning state. The WorstOf algorithm indicates that the monitor will reflect the state of its “least health” child monitor. For example, if one child is at a warning state and the other is healthy, the reflected state will be a warning state.

The Percentage algorithm indicates that the monitor will roll up the best specified percentage of members. However, the state of the monitor will reflect the worst state of that group. When using the percentage algorithm, you must include an AlgorithmParameter (DependencyMonitor) element that specifies the percentage amount.

To see how the BestOf or WorstOfAlgorithm element is expressed in a management pack, see DependencyMonitor.

Example

The following sample XML illustrates a dependency monitor that uses the percentage algorithm. It examines the best 60% of the monitors in the group. However, the resulting state of the dependency monitor will be the worst state in that group.

<DependencyMonitor ID="Microsoft.Exchange.AvailRollupMonitor" Accessibility="Public" Enabled="true" Target="Microsoft.Exchange" ParentMonitorID="SystemHealth!System.Health.AvailabilityState" Remotable="true" Priority="Normal" RelationshipType="Microsoft.Exchange.contains.Microsoft.Exchange.ServiceComponent.Organization" MemberMonitor="SystemHealth!System.Health.AvailabilityState">
  <Category>Custom</Category>
  <Algorithm>Percentage</Algorithm>
  <AlgorithmParameter>60</AlgorithmParameter>
  <MemberUnAvailable>Error</MemberUnAvailable>
</DependencyMonitor>

Share via