January 17, 2021
Hot Topics:

Developing Microsoft System Center Operations Manager 2007 Management Packs

  • By Jeffrey Juday
  • Send Email »
  • More Articles »

Setting the version requires some additional coding. $Data allows you to see properties from discovered information.

Click here for a larger image.

Figure 6: FindTestGenerateEvents Version property

At this point, Operations Manager has a Service Model (Class) and a means to discover the application. Now all you need is to do is build some monitoring.


The Health Model for the sample is defined below.

Figure 7: TestGenerateEvents Health Model

The Health of an application is based on a roll-up of each of the components above. Monitors can have two or more states. Typically, states are "Warning," "Healthy," and "Critical." Most applications will have multiple monitors under each Health Model category and may define monitors for completely need categories. Below is a monitor called TestDevelopment.EventLog.

Click here for a larger image.

Figure 8: EventLogTest monitor

All the options are defined using a new monitor wizard. The sample uses the Simple Event Wizard accessible from the Actions pane.

Click here for a larger image.

Figure 9: Creating a Simple Event Monitor

Errors in the Application event log events change the state of the monitor to "Warning." Information events change the monitor state back to "Success."

Click here for a larger image.

Figure 10: Matching Operational State to Health State

Page 4 of 6

This article was originally published on April 14, 2008

Enterprise Development Update

Don't miss an article. Subscribe to our newsletter below.

Thanks for your registration, follow us on our social networks to keep up-to-date