neebula e book root cause analysis-slideshare

6
Success Factors for Root-Cause Analysis Free eBook

Upload: kateneeb

Post on 16-Jul-2015

342 views

Category:

Technology


3 download

TRANSCRIPT

Page 1: Neebula e book   root cause analysis-slideshare

Success Factors for

Root-Cause

Analysis

Free

eBook

Page 2: Neebula e book   root cause analysis-slideshare

www.neebula .com Share this on:

Table of Contents

Why is root cause analysis important? 3

The typical NOC flow 4

Problem detection challenges 6

5 Problem detection methods 7

Selecting the right tools 9

Root cause analysis methods 10

Improving your root-cause analysis 18

Success factors for effective root cause

analysis2

Page 3: Neebula e book   root cause analysis-slideshare

www.neebula .com Share this on:

Why is Root Cause Analysis Important?

3

Root cause analysis typically concentrates on

identifying the factors that result in IT failures in

your data center.

Your ability to efficiently detect and resolve

problems affects not only your data center and IT

systems, but can also:

• Impact organizational business services

• Affect your ability to meet SLAs

• Have direct financial impact

Success factors for effective root cause

analysis

When resolving IT

problems, 80% of the time

is spent on root cause

analysis vs. 20% on

problem fixing

Page 4: Neebula e book   root cause analysis-slideshare

www.neebula .com Share this on:

The Typical NOC Flow

Success factors for effective root cause

analysis4

In the typical workflow:

• Events flow into the NOC from multiple data

sources – network events, application

events, hardware, performance monitors,

etc.

• NOC operators must then handle the flow of

all events to understand the big picture and

prioritize activities.

Typically, many of the problems are

accompanied by additional derived events. For

example, a database failure will also include

many console events related to database

connection failures, application errors, etc. NOC

operators must filter all such derived events, as

well as unrelated events on their way to identify

the cause of the problem.