New Ranks & Badges For The Community!
Notice something different? The ranks and associated badges have gone "Star Fleet". See what they all mean HERE

Configuring OMi to propagate Event KPIs with the parent displaying the sum of events

Cadet 3rd Class
Cadet 3rd Class
1 8 4,091

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.

OMi CI.jpg

 

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.

Add KPI.jpg

 

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”.

OMI CP.jpg

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.

edit KPI.jpg

 

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.

8 Comments
Not applicable

A nice simple to follow beginners guide to KPIs

It will also help to understand how the management packs are configured.

Not applicable

Nicely explained.  Thnaks Carol for educating OMi communities thorugh diffefrent sources.

Cadet 1st Class Cadet 1st Class
Cadet 1st Class

Good information.

Not applicable

Nice and easy to view instructions, very helpful.

Not applicable

Always helpful tips from these articles

Admiral Admiral
Admiral

Can you propogate more than just the most critical? Put differently, can I adjust the threshold of propagated events from critical to critical+major? Business needs may dictate doing so.

Vice Admiral
Vice Admiral

This is an interesting, different way to show how parent CIs are affacted.

Micro Focus Expert
Micro Focus Expert

csaunderson - just got your reply this week.  Looks like email delivery from this site was delayed.  Anyway...

It is not an option for the parent CI to count just critical and major because there is no option for the event KPI on the child CI.

For a CI, the count of events in the Event KPIs is based on an Infrastructure Setting (application = Operations Management) "Event Count Rule".  By default it is MOST_CRITICAL which shows a count of the highest severity events.  You can change it to either AGGREGATIVE or AGGREGATIVE_WITHOUT_NORMAL to show the count of all events or all events excluding normal severity.

Just to complete the story, the status colour of the Event KPIs is worst of the event severities on that CI.  This means, if you have AGGREGATIVE (above) and a CI has 1 critical, 4 major and 2 warning events, it would show a count of 7 in a red status.

CP.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.