Guest post by Carol Park, Operations Bridge R&D
An earlier blog article titled “OMi – Event Count based special KPIs (Unassigned Events and Unresolved Events KPIs)” explained how the Event KPIs work. Out-of-the-box they report the number of events of the highest severity on a given CI. These KPIs are not propagated from child CIs to parent CIs. Their purpose is to tell the Service Health user that there are events on that CI and to go to Event Browser to handle them.
This article explains how to configure OMi to propagate the Event KPIs to the parent and for the parent to report a sum of the most critical events for each Event KPI. The reason you might choose to do this is to emulate the default approach that was used in the Operations Manager (OM) Service Navigator or service map, namely propagating the highest severity status from child to parent.
You can visualize the result in OMi’s My Workspace such as in the 360 View as shown in the screenshot below. You can also forward the KPI status and value to OMi Business Value Dashboard.
Step 1: Decide which CI Type(s) you want to display the sum of most critical events.
For example, you might have CiCollection CIs (in the OMi Monitored Nodes UI they are also called Node Groups) for which you want to show a running total of the most critical events for all the CIs in that CiCollection. Alternatively, you might want to show such totals for each BusinessApplication CI.
Note: It is possible to apply this to all CI Types (ie, the ConfigurationItem CIT) but this might not be useful. Consider, for example, IpAddress CIs which typically don’t have either events or child CIs so Event KPIs on these CIs would be created with a permanent status of ‘Unknown’.
Step 2: Apply the Business Rule to calculate Event KPIs as the sum of the most critical events for that CI and its children, if any.
In KPI Assignments, select the CIT which you decided on in step 1 and duplicate "OMi KPI Assignments". Give the KPI Assignment a meaningful name.
Edit each of the Event KPIs and change the Business Rule from "Worst Status Rule" to "Event KPI Group And Sibling Rule (OMi)". This rule sums the number of events of the highest severity for the Event KPI on the CI and all of its child CIs.
Example: A parent CI has 2 children with events. Child1 has 1 critical and 4 major. Child2 has 2 major and 1 normal. The parent will show “1 critical”. Once that event is resolved it will show “6 major”, since that is the next highest severity in the group.
Step 3: Apply the KPI Assignment change to the existing CIs
Click “Synchronize CI Type”. This causes all existing CIs of the selected CI Type (eg, CiCollection) to get their KPI assignments updated. Any CIs added after this time get the new KPI assignment automatically.
If you later decide you want to back out these changes, you can select the KPI Assignment you created to override the default and click “Stop” or delete it altogether, and then click “Synchronize CI Type”.
Step 4: Format the value displayed for the Event KPIs
In the KPI Repository, edit the “Unassigned Events” KPI. In the Presentation Settings section, select getIntValue as the formatting method. This will format the number of events as an integer. Eg, 2 rather than 2.0.
Repeat the above for the “Unresolved Events” KPI. By making the change in the KPI Repository, the change is automatically applied to these KPIs on all CIs.