OnDemandDetection

Article
05/16/2012

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

Represents an on-demand detection workflow that is associated with one of the operational states defined in a unit monitor type.

Schema Hierarchy

ManagementPack
  TypeDefinitions
    MonitorTypes
      UnitMonitorType
        MonitorImplementation
          OnDemandDetections
            RegularDetection
              OnDemandDetection

Syntax

<OnDemandDetection MonitorTypeStateID="MonitorTypeStateID”>
  <Node ID=”ModuleID”>… </Node>
</OnDemandDetection >

Attributes and Elements

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

Attributes

Attribute	Description
MonitorTypeStateID	Required attribute. Represents the ID of the MonitorTypeState element with which this workflow is associated.

Child Elements

Element	Description
Node ( OnDemandDetection)	Required element. Represents a module in the linear operational state-based workflow.

Parent Elements

Element	Description
RegularDetection	Contains on-demand detection workflows for each of the MonitorTypeState elements defined in the unit monitor type.

Remarks

Unit monitor workflows are defined with nested Node ( OnDemandDetection) elements. Each node element is associated with any one of the modules that are listed in the MemberModules element. The inner-most node element’s module is the first step of the workflow. The outer-most node element’s module is the last step in the workflow.

If your monitor implements on-demand detection workflows, users can run the workflow and recalculate the state through the UI. In addition, when the monitored entity comes out of maintenance mode, the on-demand workflow will be automatically run in order to reflect that actual state of the monitored entity. Keep in mind, however, that if unit monitor state depends solely on system events to change state, on-demand workflows will not work as expected and should not be defined in your unit monitor type.

On-demand workflows are trigger-based and therefore always contain a ProbeAction (UnitMonitorType) module and an optional ConditionDetection (UnitMonitorType) module. If the probe action module does not return true or false from within an internal ConditionDetection module, it must follow a condition detection module that does so.

Example

The following sample shows how to define two on-demand detection workflows within a unit monitor type. Each workflow is associated with a different state of the monitor and will output data from the data sources based on what the filter conditions define.

<OnDemandDetections>
  <OnDemandDetection MonitorTypeStateID="GoodState">
    <Node ID="FirstFilterCondition">
      <Node ID="FirstProbeAction" />
    </Node>
  </OnDemandDetection >
  <OnDemandDetection MonitorTypeStateID="BadState">
    <Node ID="SecondFilterCondition">
      <Node ID="FirstProbeAction" />
    </Node>
  </OnDemandDetection >
</OnDemandDetections >
</MonitorImplementation>

Share via