Developing Microsoft System Center Operations Manager 2007 Management Packs
Below is sample Event logging code.
EventLog log; EventLogEntryType entryType = EventLogEntryType.Error; log = new EventLog("Application"); log.Source = "TestGenerateEvents"; log.WriteEntry("This error was created for testing purposes, please ignore.", entryType);
Now, you'll build a management pack to read the application instrumentation.
Creating a Management Pack
Although you can build a Management pack from within the Operation Manager console, it's easier to build the Management Pack using the Management Pack authoring console displayed in Figure 2.
Figure 2: Operation Manager Authoring Console
I used the Release Candidate version for this article. Building in the console allows you to build a Management Pack without running Operations Manager.
As stated earlier, Management Packs are XML files. So, alternatively, you can build a Management pack using an XML editor.
Management Packs usually contain one or more of the following components:
- A class is Operation Manager's representation of your application. You can build custom classes or utilize existing classes.
- Discovery identifies classes on a server and populates a class' properties.
- Monitors view the health of a class.Monitors are part of the Health Model.
Now, you'll look at how you add each of these components to the Management pack using the Authoring tool.
Classes and Class relationships define the Service Model. As stated earlier, the Service Model is essentially Operations Manager's representation of the application components and the class OO notion is similar to the OO development notion. Class physical implementation is very different than classes you define in, for example, C# development. Figure 3 shows how I defined a class TestDevelopment.MyApp with a Microsoft.Windows.UserApplication base class.
Figure 3: MyApp Class
Page 2 of 6