turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

New Era of Predictive Analytics - Service Health Analyzer

Scott_Edwards| November 28, 2011 - last edited November 29, 2011
Post a Comment

175x113_Live-Coverage.gifToday at HP Discover Vienna, HP announced a new predictive analytics tool within HP’s Business Service Management portfolio called Service Health Analyzer (SHA) that will help IT…

1.       Anticipate real IT incidents… before they occur

2.       Prevent business impact

3.       Remediate events by fusing analytics & automation

 

In a virtual and ever-changing landscape, IT operators need to make sure that the services they manage, services that enable the business to run, are working 24x7.  But with constant change, having the visibility into the health of the service is becoming ever more crucial. 

 

It used to be that IT was REACTIVE.  IT used their end-users as their monitoring system and it was the users that would notify IT that there was a problem.  IT is now becoming more PROACTIVE by deploying BSM monitoring tools to find issues and fix them quickly, tools such as synthetic and real-user monitoring as well as network and system monitoring.   But, with enterprises collecting millions of data points each day, they can often be overwhelmed with the sheer volume of information.  IT needed a way to make sense of all this data in order to become PREDICTIVE, so that they could be alerted to abnormalities and fix those issues before ever seeing service degradation.

 

“Run-Time” Predictive Analytics

HP Service Health Analyzer is ushering in a new era of predictive analytics.  Built on top of the Run-Time Service Model (RTSM), SHA enables IT managers the ability to understand the relationship of metric abnormalities with the underlying infrastructure.  Correlating these disparate metrics from both an application and a topology perspective helps you predict, or forecast, potential problems on the horizon. 

 

Because of its relationship with RTSM, SHA analyzes historical norms and trends of both applications and infrastructure, and compares that data against real-time performance metrics.  Leveraging a run-time service model is crucial for your dynamic environment so you can:

  1. Identify the suspects of an issue, and use that knowledge to prevent similar issues  in the future
  2. Correlate anomalies to topology changes and past issues
  3. Compare the current anomalies to those you’ve seen in the past, and use that information to quickly remediate and prevent similar issues in the future.
  4. Understand the business impact of each issue and prioritize resolution

 

SHA automatically learns the dynamic thresholds in your environment so you don’t have to invest the labor to set and maintain static thresholds.  SHA learns what normal behavior is in your environment by analyzing the metrics from the following BSM data sources:

  • HP Business Process Monitor
  • HP Real User Monitor
  • HP Diagnostics
  • HP Network Node Manager i
  • HP Operations Manager, Performance Agent
  • HP SiteScope
  • And 3rd party data

 

SHA will identify anomalies based on abnormal metric behavior related to the Run-Time Service Model,  set a performance analytics KPI and generate an event that has additional context to help identify business priority of the issue.  Additionally, SHA uses a technology called Anomaly DNA Technology to analyze the structural makeup of an anomaly.  It then compares the current anomaly with the known DNA of other anomalies. Matches provide known remediation actions without further investigation, and matches marked as noise will be suppressed.  If you have abnormalities related to a specific service, you can see the SLAs, and know the impact that anomaly could cause. 

 

Finally SHA incorporates remediation capabilities from the HP CLIP (Closed-Loop Incident Process) solution and provides direct integration with HP Operations Orchestration. This means, you can fuse analytics and automation together to remediate issues quickly.  When SHA sends an event into OMi or other event subsystem, an operator can take action before service is impaired with the CLIP process.  This quick remediation solution simplifies the complexities of virtualization, cloud computing environments.

 

By implementing Service Health Analyzer in your environment, you can now go from being REACTIVE, to PROACTIVE, to now PREDICTIVE.  To learn more, check out the Service Health Analyzer web page.

 

Related Links:

Tags: Analytics| BSM| Service Health Analyzer| Service Intelligence| SHA View All (5)
Leave a Comment

We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours

To ensure your comment is published, be follow the community guidelines.
Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
 
About the Author(s)


Follow Us
Labels