Management Pack Health Model Exercise #1 - Creating an Event Monitor - TechNet Articles - United States (English) - TechNet Wiki

This document is part of the Operations Manager Management Pack Authoring Guide

Overview
Authoring Console Procedure
Visual Studio Authoring Extensions Procedure
See Also

Overview

The following procedure shows how to create an event monitor using the Operations Manager 2007 Authoring console and Visual Studio Authoring Extensions.

Product Versions

This exercise applies to the following products:

System Center Operations Manager 2007 R2
System Center 2012 Operations Manager
System Center 2012 Operations Manager SP1

Prerequisites

Before you perform this procedure, you must first complete the following prerequisite procedures:

Creating a New Management Pack - Create the management pack.
Creating a Class - Create the class that is the target of the monitor.

Revisions

The Microsoft System Center team has validated this procedure as of Revision #2. 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

Sample Code

A sample of the completed code for each exercise is available in the TechNet Gallery. There is a separate sample for each exercise that includes the management pack completed at the end of that exercise and each preceding exercise. This strategy allows you to work through each exercise in order and then compare your results. For VSAE, this also includes the Visual Studio solution.

Details

The event monitor created in this procedure has the following characteristics:

Runs on any computer that has an instance of MyComputerRole1.
Sets the monitor to a critical state when an event in the Application event log with an event source of MyApplication and an event number of 101 is detected.
Sets the monitor to a healthy state when an event in the Application event log with an event source of MyApplication and an event number of 102 is detected.

Authoring Console Procedure

In the Authoring Console, select Health Model, and then select Monitors.
In the Monitors pane, expand Computer Role 1, and then expand System.Health.EntityState.
Right-click System.Health.AvailabilityState, select New, select Windows Events, select Simple, and then select Event Reset.
On the General page, do the following:
1. In the ElementID box, type MyMP.Monitor.MyApplicationEventError.
2. In the Display Name box, type MyApplication Event Error.
3. In the Target box, select MyMP.MyComputerRole1.
4. In the Parent Monitor box, select System.Health.AvailabilityState.
5. In the Category box, select AvailabilityHealth. Click Next.
On the Event Log (Unhealthy Event) page, do the following:
1. In the Log Name box, keep the default value of Application.
2. Click Next.
On the Event Expression (Unhealthy Event) page, do the following:
1. For the Event ID value, type 101.
2. For the Event Source value, type MyApplication.
3. Click Next.
On the Event Log (Healthy Event) page, do the following:
1. In the Log Name box, keep the default value of Application.
2. Click Next.
On the Event Expression (Healthy Event) page, do the following:
1. For the Event ID value, type 102.
2. For the Event Source value, type MyApplication.
3. Click Next.
4. In the Log Name box, keep the default value of Application.
5. Click Next.
On the Event Expression (Unhealthy Event)

Expand System.Health.AvailabilityState.
Right-click MyMP.Monitor.MyApplicationEventError and select Properties.
On the Health tab, for FirstEventRaised, change the Health State to Critical.
On the Alerting tab, check Generate alerts for this monitor.
Click OK.

Visual Studio Authoring Extensions Procedure

Create the Monitor:

In Solution Explorer, right click Right click the name of the project, select Add and then select New Item.
Select Monitor (Unit).
Change the name of the template to Monitors.mptg and click Add.

Configure the Monitor Properties:

Right click the entry for NewUnitMonitor and select Properties Window.
Change the ID to Monitor.MyApplicationEventError.
Change the Display Name to MyApplication Event Error.

Select the Monitor Target:

Select Target and click the ellipse (...) button on the right of the field.
Select MyMP.MyComputerRole1 and click OK.

Select the Monitor Type:

Select Monitor Type ID and click the ellipse (...) button on the right of the field.
Select Microsoft.Windows.2SingleEventLog2StateMonitorType and click OK.
Select Parent Monitor ID and click the ellipse (...) button on the right of the field.
Select System.Health.AvailabilityState and click OK.

Configure the Monitor:

Select Monitor Configuration and click the ellipse (...) button on the right of the field.
Copy the following XML into the configuration window between the <Configuration> tags. Note that you can use Intellisense to manually type in each entry.



<FirstComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</FirstComputerName>



<FirstLogName>Application</FirstLogName>



<FirstExpression>

  <And>

    

    <Expression>

      <SimpleExpression>

        <ValueExpression>

          <XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>

        </ValueExpression>

        <Operator>Equal</Operator>

        <ValueExpression>

          <Value Type="UnsignedInteger">101</Value>

        </ValueExpression>

      </SimpleExpression>

    </Expression>

    

    <Expression>

      <SimpleExpression>

        <ValueExpression>

          <XPathQuery Type="String">PublisherName</XPathQuery>

        </ValueExpression>

        <Operator>Equal</Operator>

        <ValueExpression>

          <Value Type="String">MyApplication</Value>

        </ValueExpression>

      </SimpleExpression>

    </Expression>

  </And>

</FirstExpression>



<SecondComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</SecondComputerName>



<SecondLogName>Application</>
  </And> </FirstExpression>           <SecondExpression>   <And>          <Expression>       <SimpleExpression>         <ValueExpression>           <XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>         </ValueExpression>         <Operator>Equal</Operator>         <ValueExpression>           <Value Type="UnsignedInteger">102</Value>         </ValueExpression>       </SimpleExpression>     </Expression>          <Expression>       <SimpleExpression>         <ValueExpression>           <XPathQuery Type="String">PublisherName</XPathQuery>         </ValueExpression>         <Operator>Equal</Operator>         <ValueExpression>           <Value Type="String">MyApplication</Value>         </ValueExpression>       </SimpleExpression>     </Expression>   </And> </SecondExpression>
Select Monitor Operational States and click the ellipse (...) button on the right of the field.
Next to FirstEventRaised, select Critical.
Next to SecondEventRaised, select Healthy.
Click OK,
Save and Compile the Project: Select File, and then click Save Monitors.mptg. Select Build and then Build Solution. Ensure that you don't receive any errors.
See Also Unit Monitors Events >

</SecondExpression>

Select Monitor Operational States and click the ellipse (...) button on the right of the field. Nextl>

C 2015 Microsoft Corporation. All rights reserved. Terms of Use Trademarks Privacy Statement [Copied from] v5.6.915.0 This page has been extacted by Pete Laker, Microsoft Azure MVP & Microsoft IT Implementer X