IT Operations Management (ITOM)

How to Boost Your ROI Using the HP Service Health Analyzer 9.20 Statistics Page

How to Boost Your ROI Using the HP Service Health Analyzer 9.20 Statistics Page



Blog written by Shimrit Yacobi of HP Software R&D.


HP Service Health Analyzer (SHA) represents a new era of analytics, enabling organizations to anticipate, prevent, and remediate IT incidents before they impact the business.

The SHA Statistics page helps you maximize your usage of SHA, in order to increase your ROI (Return on Investment). 

The SHA Statistics page displays a calculated ROI based on information gathered from the environment where SHA is running, and from cost parameters defined by the application administrator.

This article focuses on how you can use the SHA Statistics page in order to boost your SHA performance and increase ROI.


The starting point of the SHA Statistics page is the “Overall efficiency“  progress bar.


SHA ROI Blog  Overall Efficiency.jpg


This bar measures the current use of SHA verses the recommended use, in order to encourage you to improve your usage of SHA and increase your ROI.

For example, let’s take Bill, a BSM administrator, who has deployed SHA.

Is Bill using SHA as efficiently as possible?

Is he benefiting from all the advantages SHA has to offer?


To answer this question, Bill enters the SHA Statistics page and looks at the “Overall efficiency” section.

As long as the progress bar shows less than 100%, Bill can get more bang for his buck and increase his ROI.

How can Bill use SHA wisely and improve his ROI?


  1. CI Selection

First, Bill needs to select CIs in order for SHA to start working. Selecting CI on the CI Selection tab triggers SHA to start working. After SHA collects data and calculates metrics, Bill sees the system processing CIs in the “Metrics Management” section on the Statistics page. For details, see How to get values from SHA within 2 days.

After Bill selects CIs, SHA starts detecting anomalies.


2. Anomaly patterns


After SHA has detected a number of anomalies, Bill can proceed and improve “Anomaly patterns”. Bill sees a recommendation to define 2 investigations.

For example, suppose Bill is experiencing a failure of transactions in one of his applications. SHA detects this as an anomaly, and Bill saves this anomaly as a pattern of a known issue, with remediation instruction on how to fix this. When the problem re-occurs, SHA automatically detects that it matches a pattern and offers the remediation to Bill, dramatically reducing the time required to repair the problem.

It is important to note that SHA will find similar problems not only on the same transaction but also on other transactions and other applications based on a patented similarity anlaysis employed by the system, thereby spreading IT knowledge across the customer organization, and saving time in remediating the problem.


3. Verification Tools


Verification tools help Bill isolate the root cause of problems.

The verification tool is an on-demand SiteScope monitor that runs when an SHA anomaly is detected.

Verification tools run for each CI in the topology which is associated with the anomaly. When a verification tool fails, the CI it ran on is marked as a possible root cause of the problem.


Overall Efficiency – Summary:

By applying SHA’s recommendations for each section, Bill can experience a significant improvement in termsof ROI and money saved.


Where is the ROI displayed?

The “Metrics Management” and “Event and Anomalies” sections represent the ROI for SHA.


Metrics Management

One key area of SHA ROI is the reduced administrative effort of setting and maintaining thresholds. The “Metrics Management” section calculates ROI by estimating the administrative overhead of maintaining thresholds.


SHA ROI Blog  Metric Management.jpg


Events and Anomalies

This section looks at ROI from an event-reduction perspective, comparing the current events stream with the anomaly events which  are generated from SHA.

SHA ROI Blog  Event Anomolies.jpg 

The graph displays a comparison of the number of events, with the number of detected anomalies. The monthly saving represents the amount saved when handling only SHA events vs.  each one of the events  


The “Metric Management” and “Event and Anomalies” information is combined into the savings of the SHA Statistics:


SHA ROI Blog  RoI.jpg






In  today’s dynamic environments, the complexity, time, and effort spent solving problems can grow very quickly. With SHA you can reduce your costs and improve your efficiency


  • operational intelligence
0 Kudos
About the Author