This document is part of the Operations Manager Management Pack Authoring Guide.  The Microsoft System Center team has validated this procedure as of the original version.  We will continue to review any changes and periodically provide validations on later revisions as they are made.  Please feel free to make any corrections or additions to this procedure that you think would assist other users.

Monitors and rules are the primary elements of a health model and provide similar yet distinct functionality. Monitors set the state of a monitored object, whereas rules create simple alerts and collect data for analysis and reporting. Each monitor and rule is defined by the source of the data that was used to perform its required functionality and the logic to evaluate this data.

Although they provide different functionality, monitors and rules use a common set of sources that provide the data to evaluate. For example, a monitor may use a performance counter to set the state of a particular object. A rule may access the same performance counter in order to store its value for analysis and reporting. The following sections provide the details of each different kind of data sources that may be used in monitors and rules.

The data sources and monitoring logic discussed in this section are those that can be created by using wizards in the Authoring console. Other data sources and logic can be implemented by creating custom modules and workflows as discussed in the Composition section of this guide.

See Also