IT Operations Management (ITOM)
cancel

OMi: Looking Beyond Event Severity for Prioritization

OMi: Looking Beyond Event Severity for Prioritization

Mgoyal

If there are hundreds of critical or high-severity events open in the event browser, how do you prioritize which one is most important? Usually, it comes down to subjective judgement - but that doesn't need to be the case. In OMi, there is something called event “Priority”, and it can be of great help in prioritizing events.

Event Priority:

  • It is a calculated attribute based on the severity of the event and the business impact of the event. Calculation is done automatically for the new events in the event pipeline and it can also be invoked manually in the operator console menu.
  • Possible values of this attribute are “Lowest”, “Low”, “Medium”, “High” and “Highest”.
  • For business impact calculation, event must have a related CI and if an event does not resolve to a related CI, priority attribute of such event is not set.

Click here to sign up for the HPE Software monthly newsletter!

Following screen shot shows the priority column in the OMi Event Browser:

Priority-screen.PNG

 

The table below shows how the Priority attribute is calculated:

priority-table.png

We all know about the severity attribute that is set by the monitoring source, but what is this business impact - the other component that goes into “Priority” calculation?

Business Impact (or just Impact):

Business Impact value indicates how much impact a selected CI has on the business entities and SLAs impacted by it. The impacted business entities are the business CIs (like Business Application CIT, Business Service CIT and Business Process CIT) according to the RTSM impact model.

By default, business impact is calculated based on the following metrics:

  • Criticality of the impacted business CIs as defined by the “BusinessCriticality” attribute of the business CI (in RTSM, each business CI can have this attribute defined with a value between 1 to 5 )
  • Number of impacted business CIs
  • Number of impacted SLAs (NOT APPLICABLE for OMi 10.x as there is no SLM in OMi 10.x)

Each metric can be enabled/disabled to be used for business impact calculation purpose. Once enabled, it is further possible to assign relative weights and thresholds to customize the calculation.

NOTE: For related CIs that do not have “BusinessCriticality” attribute or that do not impact any business CIs, business impact value is taken as “NoImpact” and hence the first row in the above table will be applicable for Priority calculation purpose.

Default Settings:

  • All the three metrics are enabled to be included in the calculation
  • All metrics have equal weightage in the calculation
  • For BusinessCriticality of impacted Business CIs metric, the highest degree of criticality among all the impacted business CIs is used; For example, if a CI impacts three business CIs with criticality values of 5, 3 and 1, then the value used in calculation, as per default rule, will be 5.
  • For the metrics - number of impacted business CIs or SLAs, the rating is based on the percentage of impacted CIs/SLAs from the total number of relevant CIs/SLAs in the environment. For example, if a CI impacts 2 business CIs out of 10 business CIs in the model, the CI has a rating of 1 (or 20% on the rating scale of 1 to 5).

Customization of Business Impact Calculation:

This can be done by editing an xml file accessible from Admin -> Infrastructure Settings by selecting Applications -> Business Impact Service.

The file contents look as below:

<context category="applications" name="BIZAppSettings" nameResource="BIZAppSettings">

<config>

<rules>

                <rule class="com.hp.am.bac.bis.evaluators.rules.WorstRule" id="1" type="Worst"/>

                <!-- <rule type="Best" id="2" class="com.hp.am.bac.bis.evaluators.rules.BestRule"/> -->

                <rule class="com.hp.am.bac.bis.evaluators.rules.AverageRule" id="3" type="Average"/>

</rules>

<metrics>

                <metric class="com.hp.am.bac.bis.evaluators.calculators.CalculatorBasedOnNumOfBusinessEntities" id="BasedOnNumOfBusinessEntities" ruleId="1" weight="1">

                                                               

                                <thresholds>

                                                <!--

                                                <threshold value="5" valueMapping="20" />

                                                <threshold value="6" valueMapping="80" />

                                                <threshold value="7" valueMapping="90" />

                                                <threshold otherwise="90" />

                                                -->

                                </thresholds>

                </metric>

                <metric class="com.hp.am.bac.bis.evaluators.calculators.CalculatorBasedOnNumOfSLAs" id="BasedOnNumOfSLAs" ruleId="1" weight="1">

                                <thresholds/>

                </metric>

                <metric class="com.hp.am.bac.bis.evaluators.calculators.CalculatorBasedOnCriticality" id="BasedOnCriticality" ruleId="1" weight="1">

                                <thresholds/>

                </metric>

                </metrics>

</config>

</context>

 

  • There are three metrics classes as mentioned before, each with weight, ruleId and thresholds settings
  • The “weight” setting of greater than 0, in the highlighted lines of the file above, enables the metric while a value of 0 disables the use of that metric. Also, a value of more than 1 indicates the relative weight of the corresponding metric in the final calculation, when more than 1 metrics is in the picture.
  • “ruleId” is applicable for “basedonCriticality” metric. The default behavior of using the worst criticality rule, can be changed to average criticality of all the impacted business CIs by changing the ruleId value to 3 in the corresponding line
  • When all three metrics are used in the calculation with a default weight equal to 1, then all three have equal weightage but if you want to assign different weights to different metrics, that can be done by changing the value of “weight” in the above lines. Lets take an example to understand how it affects the impact calculation:   

Suppose you define that ratings are based on criticality with a weight of 5, and on the number of SLAs with a weight of 2. If a given CI's rating based on criticality alone would be 4, and based on SLAs alone would be 1, the overall rating is calculated as (4x5) + (1x2) / 7 = 3.14. The business impact rating is therefore 3 (medium).

  • For the number of impacted business CIs/SLAs metrics, the thresholds values can be customized such that if a specific number of CIs or SLAs are impacted by a CI, this is mapped to a specific rating. As an example consider the following settings:

<threshold value="5" valueMapping="20" />

<threshold value="6" valueMapping="80" />

<threshold value="7" valueMapping="90" />

<threshold otherwise="90" />

 This means that if a CI impacts 5 CIs, its business impact is mapped to 20%, giving it a rating of 1 (out of 5). If this CI impacts 6 CIs, its rating is 4 (80% translated on a scale of 5) and if it impacts 7 or more CIs, its rating is 5 (90% translated on a scale of 5).

 Remember, that this mapping defines the business impact rating, independent of the total number of business CIs or SLAs in your environment unlike default mapping which is based on %age of impacted CIs/SLAs in the model.

Event Priority is a very useful attribute, even without any customization – make use of it. Just make sure your business CIs are set with appropriate value in “BusinessCriticality” attribute.


 

Click here to sign up for the HPE Software monthly newsletter!

 

  • operations bridge
About the Author

Mgoyal

Comments
N/A

Sounds very logical everything  explained in this article , My first impression: I  love how the product works ; but what frightens me is to apply this in a large enterprise company, the first step: establish the qualification criteria of each IC.

//Add this to "OnDomLoad" event