Monitors

Article
10/04/2013

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

Contains monitor definitions targeted at a specific class type.

Schema Hierarchy

ManagementPack
Monitoring
Monitors

Syntax

<Monitors>
   <AggregateMonitor ID=”MonitorID” Comment=”Comment” Accessibility=”Public/Internal” Enabled=”True/False” Target=”TargetClassID” ParentMonitorID=”MonitorID” Remotable=”True/False” RunAs=”SecureReferenceID” Priority=”Normal”>…</AggregateMonitor>
   <UnitMonitor Id=”UnitMonitorID” Comment=”Comment” Accessibility=”Public/Internal” Enabled=”True/False” Target=”TargetClassID” ParentMonitorID=”ParentMonitorID” Remotable=”True/False” Priority=”Normal” RunAs=”SecureReferenceID” TypeID=”UnitMonitorTypeID”>…</UnitMonitor>
   <DependencyMonitor Id=”DependencyMonitorID” Comment=”Comment” Accessibility=”Public/Internal” Enabled=”True/False” Target=”TargetClassID” ParentMonitorID=”ParentMonitorID” Remotable=”True/False” Priority=”Normal” RunAs=”SecureReferenceID” RelationshipType=”RelationshipTypeID” MemberMonitor=”RollupMonitorID”>…</DependencyMonitor>
</Monitors>

Attributes and Elements

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

Attributes

None.

Child Elements

Element	Description
AggregateMonitor	Optional. Defines a state machine whose health state is determined by an algorithmic analysis of its children.
UnitMonitor	Optional. Defines an implementation of a unit monitor type definition that determines the health of targeted class type instances.
DependencyMonitor	Optional. Defines a state machine whose health state is determined by an algorithmic analysis of a hosting or containment relationship’s target instances.

Parent Elements

Element	Description
Monitoring	Contains the workflow definitions that are used to discover and monitor the service model of a management pack.

Remarks

The Monitors element of a management pack contains the state-based monitors of your health model. Two of the monitor types, AggregateMonitor and DependencyMonitor, are monitors that roll up other monitors (including other dependency and aggregate monitors). Use these types to create the appropriate hierarchy of your application’s health model. The UnitMonitor element is a monitor that implements a UnitMonitorType definition and targets a specific aspect of a class type to monitor. Unit monitor types always roll up to one of the other two monitor types.

Share via