Problem Isolation 8.

0
Assaf Dagan
R&D team manager

© 2006 Hewlett-Packard Development Company, L.P.

The information contained herein is subject to change without notice
Agenda
• Reactive Analysis
• Proactive Analysis
• Installation tips
• Q&A

2 19 August 2009
Reactive Analysis user persona
NOC/Application support team
• Receives incident indications
in the Dashboard and/or
through alerts
• Needs to know quickly what
domain is the real owner of
the incident
• Not a subject-matter expert

Reduce application downtime and eliminate finger-pointing by quickly

identifying the root cause and escalating to the right domain owner

HP Private
Reactive Analysis flow
Service Manager Dashboard/Alert

Incident ID/CI ID Find problem

CI ID
start time

Problem already
isolated based on CI
and start time?

Continue existing Start a new

isolation isolation

Find problem
suspects

Run on-
Revalidate Perform metric
demand
problem (?) correlation
monitors (?)
Proactive Analysis user persona
The Problem Manager

• Needs to track and solve

underlying root causes, not
work around them
• Periodically reviews historical
data and looks for trends
• Sometimes performs this
function on a part-time basis

At your convenience, utilize automated analysis of data to make “an ounce of

prevention worth a pound of cure” (Benjamin Franklin)

HP Private
How does proactive analysis work?
1. Runs daily as a scheduled task and Analyze
application behavior
2. Run data segmentation algorithm on
transactions
3. Find anomalies
4. Analyze correlation between system metrics
and application anomalies
Behavioral anomaly
Temporary detected, although
spikes are threshold was not
ignored breached
memory