Export (0) Print
Expand All

How to Create a Monitor

Updated: May 22, 2009

Applies To: Operations Manager 2007 R2, Operations Manager 2007 SP1

You can use monitors to determine the health state of an application component. Monitors are an integral part of the health model, as they are the "intelligence" of Operations Manager. They look at monitoring information and determine whether the application is healthy.

This topic will show how to use the authoring console to create a two-state event monitor.

noteNote
This topic assumes that you are using the management pack created in the How to Create a Management Pack With a Discovery Using the Windows Registry Template topic.

Creating the Monitor

  1. Select the Health Model area in the authoring console main window, and then click Monitors in the navigation tree.

    b7b82241-a994-4909-9881-b1ecafb27ee9
  2. Find the class that was created in the How to Create a Management Pack With a Discovery Using the Windows Registry Template topic. This class name is AuthoringConsole.MyFirstMP.LOBApplication.

    Right-click the class, click New, click Windows Events, click Simple, and then click Event Reset. The Event Reset Wizard starts.

  3. In the Element ID text box, enter AuthoringConsole.MyFirstMP.MonitorConnectionState

  4. In the Display Name text box, enter LOB Application connection state

  5. In the Target drop-down list, click AuthoringConsole.MyFirstMP.LOBApplication

  6. In the Parent Monitor drop-down list, click System.Health.AvailabilityState

  7. In the Category drop-down, click StateCollection

    805efe0b-3eac-4bf7-8dbe-c0703977f3ad
  8. Click Next.

  9. On the Event Log (Unhealthy Event) page, leave Application as the name of the log for the unhealthy event, and click Next.

  10. On the Event Expression (Unhealthy Event) page, set the Event ID equal to 201, and the Event Source to EventCreate, then click Next.

    c5d6abb0-8608-40f7-9d46-8d01f17b14d2
  11. On the Event Log (Healthy Event) page, leave Application as the name of the log for the unhealthy event, and click Next.

  12. In the Event Expression (Healthy Event) page, set the Event ID equal to 202, and the Event Source to EventCreate, then click Finish to create the monitor and return to the Monitors list.

    af194526-8f15-47de-8185-e5849f596df8
  13. Save the management pack by clicking File, and then clicking Save from the authoring console main menu.

  14. View the properties for the monitor that was just created by expanding the monitor tree view (if necessary), right-clicking the monitor we just created, and clicking Properties, and then clicking the Alerting tab.

    31448451-d5c3-4090-8e9a-9cfe5dd6f984
  15. Click the Generate alerts for this monitor check box, select The monitor is in a warning health state from the Generate an alert when drop-down list, and then click OK.

  16. Save the management pack by clicking File, and then clicking Save from the authoring console menu.

You have now created a two-state event monitor that will show the health state of the LOB application class.

See Also

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft