Operations Manager offers a variety of tools for creating management packs, of which the VMPD is only one. Depending on the complexity of your system or your application, the VMPD might not be the right tool for you. If this is the case, then you should
use the Visual Studio Authoring Extentions or the Operations Manager Authoring Console.
When your application fits one of the patterns provided: single-server patterns for single server roles or groups, with or without components; or distributed applications, two-tier or three-tier, with individual servers or computer groups.
When your monitoring needs fall within the bounds of the five performance monitors the VMPD provides: Performance monitoring, Event monitoring, Service monitoring, Web site monitoring, and Database monitoring. However, those monitors are subject to some
limitations, described below.
If your monitor is based on a script. The monitoring shapes that are part of the VMPD provide a wide range of monitoring features but do not support script-based monitoring at this time.
If your monitor requires logic that is not available in an existing shape. For example, you may want an event monitor that checks an application log at specific intervals and looks for a heartbeat event. If that event does not appear for a certain period
of time, you’d want to raise an alert. There is not currently a missing event monitor in the VMPD.
The Visio Management Pack Designer builds management packs based on the schema for Operations Manager 2007 R2. This format is compatible with System Center 2012 Operations Manager (which is currently in beta), so any management packs built with the tool
will work with either version of the product.
The VMPD provides Visio stencils with shapes that represent management pack classes or monitoring scenarios. You can create a Visio diagram using shapes that represent your application and the monitoring it requires. Each of the shapes has properties that
allow you to configure its details. When you select the option to generate the management pack, code behind each of the shapes is executed in order to generate the management pack XML Each shape may generate one or more management pack elements depending
on the selected options. For example, a Server Role shape will create a
management pack class, the
discovery required to create instances, and a
state view to display discovered instances.
You should treat the Visio drawing as the source code of your management pack. There is no way to import an existing management pack into the VMPD. If you want to make any changes after the management pack is created, you should make the changes to the
drawing and then import the updated management pack into the management group.
Because the Visio Management Pack Designer does not include every possible monitoring scenario or the ability to create such elements as custom views and groups, you may require additions to the management pack using other tools. For example, you may want
to create a script monitor using the Operations Console after you install the management pack into a management group. If you do make changes in Visio after making changes to the management pack using the other tool, then you will overwrite those changes when
you install the updated management pack.
The solution to this issue is the
seal the management pack before installing it. Any additional elements can be stored in a separate management pack using the classes created in the management pack created with the VMPD.
Before you can install the Visio Management Pack Designer, you'll need the following prerequisites:
* To design an MP you can use Visio 2010 SP1 Professional but if you want to “compile” (create) the actual management pack XML you need
Visio 2010 SP1 Premium. So working in a team doesn’t really require everyone to install the Premium edition, just the one who compiles the MPs.
Us the following procedure to install the VMPD.
When you select a shape, the properties for that shape will be displayed in the Shape Data window. If the
Shape Data Window is not visible, then use the following procedure to display it.
When you add a monitor to a drawing, it must be connected to a modeling shape. The monitor will run on all agent computers where the target class is discovered. Use the following procedure to attach a monitor to a shape.
You can connect modeling shapes in a diagram in order to configure health rollup between classes in the management pack. Health rollup causes the health of one object to be dependent on the health of another object. For example, you may have a Server Component
shape that has a health rollup to a Server Role shape representing the server that the component resides on. Further details on this concept is discussed in
Dependency Monitors.Use the following procedure to configure health rollup between modeling shapes.
The VMPD will return an error if you attempt to generate a management pack from a drawing if there with incorrect configuration. You can validate that a drawing meets the requirements by using the following procedure.
Use the following procedure to generate a management pack.
Once the management pack has been created, you should
seal it before
installing it in the management group as explained above in Maintaining the Management Pack.
The functionality of the VMPD is determined by the shapes that are used in the diagram. The following references provide details of the shapes that are currently available.
Example is available that walks through creation of a management pack using the VMPD.