03 December 2012 blogs Michiel Rens 3 min read
In a previous blog article the most frequently used methods in overriding the Health Rollup on a Live Maps view have been explained, but that won’t help us resolving the Health Rollup for non-default aggregation categories. In this blog article I will explain the option to further extend the Health Rollup on a Live Maps view to include additional aggregation categories.
How-To: Include non-default aggregations in the Health Rollup on a Live Maps view
In both System Center Operations Manager 2007 and 2012, Unit Monitors as defined in Management Packs do rollup their Health State to a parent Aggregate Rollup Monitor. Most monitors will fall into one of the four categories as defined in the System Health Library: Availability, Configuration, Performance or Security. The Health Rollup on a Live Maps view, which provides the consolidated health of all objects on a Live Maps view, adhers to this same logic and defines the Health Rollup to occur in these same four commonly used categories:
But how to handle a situation where a Management Pack introduces an additional aggregation category and includes monitors that do set the state of the monitored object in this non-default aggregation category?
The aggregated health state of the object (Entity Health) will properly reflect any Health State changes set by the Unit Monitors in this category, but the Health Rollup on a Live Maps view will not include this newly introduced aggregation category and will determine the consolidated health state of all objects shown based on just the default Availability, Configuration, Performance and Security aggregation categories.
To get any (current and future) non-default category to rollup to the consolidated Live Maps view health too, an additional Dependency Rollup Monitor can be created to separately rollup the consolidated Entity Health of all objects on a Live Maps view as well:
When this Dependency Rollup Monitor targets the Live Maps Group class, it will automatically apply to all (current and future) Live Maps views directly. In the Authoring Pane of the Operations Console the added Dependency Rollup Monitor will show as follows:
In the Management Pack that comes with this blog artcle, a Dependency Rollup Monitor named Live Maps Entity Health is defined, which targets the Live Maps Group class. The sealed version of the Management Pack will be required when overrides on the defined Dependency Rollup Monitor are to be created. A description on how to define overrides for the Health Rollup on a Live Maps view is provided in this blog article.