Distributed Applications Custom MP

If you have begin to work with distributed applications, you have begun to work with one of the most impressive areas of Operations Manager. This is the facility that allows you to truly take the health model approach to the next level. Essentially, it is a graphical tool that allows you to model your infrastructure along service boundaries, as opposed to the physical boundaries to which we have always been accustomed.

Behind the scenes, Operations Manager creates many entities in the management pack to which you save your distributed application. These are classes, instances of those classes, relationships, monitors, etc.

I plan to blog about several facets of understanding and implementing distributed applications in the future, but one foundational element is an MP I have written that includes a new distributed application template that I think you will find useful.

It is a completely blank distributed application that will appear in the Template list when you create a new distributed application. It is very similar to the “Blank (Advanced)” template that ships with OpsMgr, but it is truly blank. It will appear as “Empty Distributed Application” in the template list.

There are two differences between my “Empty Distributed Application” template and the “Blank (Advanced)” template that ships with OpsMgr:

  1. The “Blank (Advanced)” template includes a dependency monitor named “Blank Distributed Application Health Roll-up”. This is a curious monitor for three reasons:
    1. It is a dependency monitor whose parent is Entity Health -> Availability but it makes a dependency link to the Entity Health aggregate monitor for everything in the DA. That’s somewhat redundant.  Actually, I think it would be best described as “recursively redundant,” since that gives you Entity Health -> Availability -> (this monitor) -> Entity Health -> Availability -> …
    2. The logical function of this monitor is already performed by the “All Contained Objects” dependency monitor already under Availability (hence the redundant part of my comment).
    3. This monitor is disabled.
  2. Along these same lines, my template adds a dependency monitor named “All Contained Objects” under Configuration, Performance, and Security, to match the one that is under Availability by default. These are enabled by default but can be easily overridden if desired. You may want certain DAs created from this template to be availability-only, etc., but I think the presence of the monitors will help.

The current version of the sealed MP is  Our public key token is b77a5c561934e089, though I don’t think you’ll need it for this MP; it’s probably not one you’ll re-use (no modules, etc.).

The MP is available for download here:




Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: