MonitorTypeState

Article
05/16/2012

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

Represents a possible operational state of a unit monitor type.

Schema Hierarchy

ManagementPack
  TypeDefinitions
    MonitorTypes
      UnitMonitorType
        MonitorTypeStates
          MonitorTypeState

Syntax

<MonitorTypeState ID=”StateID” Comment=”Comment” NoDetection=”True/False”/>

Attributes and Elements

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

Attributes

Attribute	Description
ID	Required attribute. Represents the identity of the state type. Must be unique within the UnitMonitorType definition.
Comment	Optional attribute. Represents commentary by the management pack author.
NoDetection	Optional attribute. Defines whether or not operational state is to be automatically detected by the monitor. Defaults to False.

NoDetection Attribute

Value	Description
True	Specifies that there is no workflow defined to determine when the operational state occurs. The operational state will only occur when manually set by the user.
False	Default value. Specifies that there is a workflow or workflows defined to determine when the operational state occurs.

Child Elements

None.

Parent Elements

Element	Description
MonitorTypeStates	Contains the definitions for possible operational states of the unit monitor type.

Remarks

Note that operational states do not automatically map to actual health states (e.g., Error, Warning, Healthy). It is up to the unit monitor implementation to map operational states to health states. Monitor implementations are found in the Monitors element of the internal or external management pack.

Example

The following sample XML illustrates the definition of three operational states.

<MonitorTypeStates>
  <MonitorTypeState ID="UnderThreshold"/>
  <MonitorTypeState ID="BetweenThresholds"/>
  <MonitorTypeState ID="OverThreshold"/>
</MonitorTypeStates>

The following sample XML illustrates the definition of two operational states, where one can only be set by the user.

<MonitorTypeStates>
  <MonitorTypeState ID="ProblemEventRaised"/>
  <MonitorTypeState ID="ResetEventRaised" NoDetection=”true”/>
</MonitorTypeStates>

It is also possible to supply only one operational state when that state’s NoDetection attribute is set to true.

<MonitorTypeStates>
  <MonitorTypeState ID="ResetEventRaised" NoDetection=”true”/>
</MonitorTypeStates>

Share via