27 March 2012 blogs Michiel Rens 4 min read
Quite frequently we receive questions on how the Health Rollup on a Live Maps view is performed and whether it is possible to make any changes to this Health Rollup to support specific customer scenarios. In this article I will explain the default Health Rollup that is performed on any Live Maps view and different options that are available to change this default behavior.
How-To: Override the Health Rollup on a Live Maps view
By default, the Health Rollup on a Live Maps view treats objects that are in a ‘Monitoring Unavailable’ state as ‘Critical’. So, when there are one or more objects in a ‘Monitoring Unavailable’ state on a Live Maps view, the consolidated Health State of that Live Maps view will show ‘Critical’.
This can be illustrated by looking at the Health Explorer output in such a situation:
By creating overrides, we can change this behavior. In the example below, an override is applied to the Monitoring unavailable parameter of the Live Maps Availability Health Rollup for the specific Live Maps view (group) named Cluster Nodes:
When we do the same on the Live Maps Configuration Health Rollup, the Live Maps Performance Health Rollup and the Live Maps Security Health Rollup and then refresh our Health Explorer output, we can see the result of these overrides being reflected in the Health Rollup that is performed:
In the example above, we have defined these overrides for a single Live Maps view (named Cluster Nodes).
If we would want to apply these overrides to all Live Maps views at once, we have to target all objects of the class Live Maps Group in our overrides definitions:
After defining an override on each of the four standard OpsMgr Health Categories (Availability, Configuration, Performance and Security), the Live Maps Health Rollup for any object on a Live Maps view that is in a ‘Monitoring Unavailable’ state will be according to the override value as specified.
Similar to the override definitions for ‘Monitoring Unavailable’ as described above, overrides can be defined that influence objects that are in ‘Maintenance Mode’. By default, objects in Maintenance Mode are rolled up as ‘Healthy’. Using overrides this can be changed to ‘Warning’ or ‘Critical’.
Rollup Algorithm and Percentage
The default ‘Rollup Algorithm’ that is used on a Live Maps view is defined as ‘Worst Health State of any member’, just like the default entity Health Rollup that is used by OpsMgr to calculate the Health State on any managed object.
In certain scenarios, it might be desired to change this algorithm. The other options available are ‘Best Health State of any member’ and ‘Worst State of a percentage of members in good Health State’.
The later needs to be combined with a value for the parameter ‘Percentage’. In the example below an override is defined for this combination:
So now its Rollup Algorithm reads ‘The worst state from 50% of the best states of the objects in this group’. A terrible definition, I know, but that is how it is defined in OpsMgr. This is what is called a most optimistic “glass half-full” scenario: it takes 50% of the objects in their best state and then rolls up the worst state of those.
When our Live Maps view ‘Cluster Nodes’ shows the following states for our individual Windows Cluster nodes:
the following Availability Health Rollup would be presented in the Health Explorer output due to the Rollup Algorithm as defined:
The Live Maps Availability Health Rollup will keep showing ‘Healthy’ in this example as long as the Availability Health of at least 50% of the objects is Healthy.
When we have 2 of the objects in a ‘Warning’ Availability state while the others are ‘Healthy’, the Live Maps Availability Health Rollup will keep showing ‘Health’ as well:
With the use of overrides, the Health Rollup on a Live Maps view can be changed to reflect the consolidated state of the objects on that Live Maps view as deemed correct from a business perspective. This is especially useful in clustering scenarios and other redundancy or High Availability solutions.
More information on Live Maps can be found here.