HPE Software is now Micro Focus
HPE Software is now Micro Focus
IT Operations Management (ITOM)

Identify and resolve problems before your users are impacted

Identify and resolve problems before your users are impacted


Guest post by Shahar Tal, Research and development team, APM and Analytics


Every business wants to identify and resolve problems before users are affected and revenue suffers.

This can easily be accomplished by integrating Service Health Analyzer (SHA) with Operations Analytics (OpsA).


SHA anticipates IT problems before they occur by analyzing abnormal service behavior and alerting IT managers of real service degradation before it impacts the business. It uses performance metrics and topology data to find anomalies, forecast problems, prioritize issues based on business impact, automatically create real thresholds, and take action before service is impaired. Operations Analytics is HP’s next generation analytics platform powered by Vertica, big data database. Operations Analytics takes SHA capabilities to a new level; it collects all IT and IT related data, including logs. It also pinpoints the cause of the problems that traditional monitoring tools are not designed to diagnose. Combination of SHA and Operations Analytics is particularly valuable to those customers who already use SHA and are ready to take the next steps towards analysis of machine data to gain longer term historical and predictive insights and more powerful troubleshooting of complex cross-domain performance problems


Bringing SHA and OpsA together provides predictive alerting regarding a business problem with the capability to drill into the underlying cause all the way down to the log message level.

To deploy this capability all you need to do is configure Operations Analytics location in SHA’s settings:


Infrastructure Settings.png


As a result you can drill down from the alert’s properties in SHA to the analysis of suspect node in OpsA.


The full flow begins by opening the investigation screen of the predictive event generated by SHA which appears in the events console, and from examining both the topology and metrics view, check the Host which is the root cause, for example the one of the DB/ application-server layer (the root cause host will usually appear in SHA’s Highlights screen).

Using SHAs drill-down capability you can move directly into OpsA:


Topology view.png


Once in OpsA you’ll see the Host dashboard, including metrics, events and the analyzed logs with the time frame already set based on the anomaly time frame:


log analytics.png

Bringing Service Health analyzer and Operations analytics together helps you preempt developing issues and resolve them before the business is impacted.

To learn more about Service Health Analyzer visit: http://www.hp.com/go/sha

You can download Service Health Analyzer here to try it for yourself.

To learn more about Operations Analytics visit: http://www.hp.com/go/opsanalytics


About the Author


This account is for guest bloggers. The blog post will identify the blogger.