DataSource (UnitMonitor)

Article
05/16/2012

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

Represents an implementation of a data source module type definition.

Schema Hierarchy

ManagementPack
  TypeDefinitions
    MonitorTypes
      UnitMonitorType
        MonitorImplementation
          MemberModules
            DataSource (UnitMonitor)

Syntax

<DataSource ID=”ModuleID” Comment=”Comment” TypeID=”ModuleTypeID”>
Custom Schema Defined Parameters
</DataSource>

Attributes and Elements

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

Attributes

Attribute	Description
ID	Required attribute. Represents the identity of the element.
Comment	Optional attribute. Represents commentary by the management pack author.
TypeID	Required attribute. Represents the DataSource module type definition from which this DataSource module inherits its configuration schema.

ID Attribute Values

Value Description

Value	Description
The format for the ID attribute should be `UniqueElementID`.	The ID string must contain the following characteristics: The length is less than 255 characters. The ID begins with a letter (a-z) or a number (0-9). The ID contains only letters, numbers, the period character (.), or the underscore (_) character. The ID is unique across all elements within the scope of the DataSource module’s containing workflow. The ID is case-sensitive.

The format for the ID attribute should be UniqueElementID.

The ID string must contain the following characteristics:

The length is less than 255 characters.
The ID begins with a letter (a-z) or a number (0-9).
The ID contains only letters, numbers, the period character (.), or the underscore (_) character.
The ID is unique across all elements within the scope of the DataSource module’s containing workflow.
The ID is case-sensitive.

Child Elements

The child element of the DataSource module is defined by the Configuration (DataSourceModuleType) schema of its base type as referenced in the TypeID attribute.

Parent Elements

Element	Description
MemberModules (DataSourceModuleType)	Contains all of the modules that are used in the linear workflow of a module type definition.

Remarks

Because a data source module does not take an input stream, it must always be the first module in any workflow. The data source module initiates the workflow functioning entirely or partially as a scheduler or functioning as a data provider. As a data provider, the data source can get data from NT performance counters, SNMP triggers, or NT events.. The data type of its output data is defined in its OutputType (ConditionDetectionModuleType) element.

A data source module type never alters system state. If you want a module to affect system state, you must use or implement a WriteAction (WriteActionModuleType) module.

A data source module’s base type must always be a descendant of a DataSourceModuleType element.

Example

The following XML sample shows a UnitMonitorType that uses two data source modules, one for each monitor state workflow. To view an implementation of the Microsoft.Windows.2SingleEventLog2StateMonitorType unit monitor type, see UnitMonitor.

<UnitMonitorType
ID="Microsoft.Windows.2SingleEventLog2StateMonitorType"
Accessibility="Public">
  <MonitorTypeStates>
    <MonitorTypeState ID="FirstEventRaised" />
    <MonitorTypeState ID="SecondEventRaised" />
  </MonitorTypeStates>
  <Configuration>
    <IncludeSchemaTypes>
      <SchemaType>System!System.ExpressionEvaluatorSchema</SchemaType>
    </IncludeSchemaTypes>
    <xsd:element name="FirstComputerName" type="xsd:string" />
    <xsd:element name="FirstLogName" type="xsd:string" />
    <xsd:element name="FirstExpression" type="ExpressionType" />
    <xsd:element name="SecondComputerName" type="xsd:string" />
    <xsd:element name="SecondLogName" type="xsd:string" />
    <xsd:element name="SecondExpression" type="ExpressionType" />
  </Configuration>
  <MonitorImplementation>
    <MemberModules>
      <DataSource TypeID="Microsoft.Windows.EventProvider"
      ID="FirstDataSource">
        <ComputerName>$Config/FirstComputerName$</ComputerName>
        <LogName>$Config/FirstLogName$</LogName>
      </DataSource>
      <DataSource TypeID="Microsoft.Windows.EventProvider"
      ID="SecondDataSource">
        <ComputerName>$Config/SecondComputerName$</ComputerName>
        <LogName>$Config/SecondLogName$</LogName>
      </DataSource>
      <ConditionDetection TypeID="System!System.ExpressionFilter"
      ID="FirstFilterCondition">
        <Expression>$Config/FirstExpression$</Expression>
      </ConditionDetection>
      <ConditionDetection TypeID="System!System.ExpressionFilter" ID="SecondFilterCondition">
        <Expression>$Config/SecondExpression$</Expression>
      </ConditionDetection>
    </MemberModules>
    <RegularDetections>
      <RegularDetection MonitorTypeStateID="FirstEventRaised">
        <Node ID="FirstFilterCondition">
          <Node ID="FirstDataSource" />
        </Node>
      </RegularDetection>
      <RegularDetection MonitorTypeStateID="SecondEventRaised">
        <Node ID="SecondFilterCondition">
          <Node ID="SecondDataSource" />
        </Node>
      </RegularDetection>
    </RegularDetections>
  </MonitorImplementation>
</UnitMonitorType>

Share via