optimising devops: pre-empting failure

30
www.ranger4.co m DevOpstasti c Optimising DevOps 3) Pre-empting Failure

Upload: ranger4-limited

Post on 20-Jun-2015

309 views

Category:

Technology


2 download

DESCRIPTION

Part of our DevOps trio of tools for change. In this slide deck we take a better look at Application Performance Management (APM) and how it can help with pre-emting failures.

TRANSCRIPT

Page 1: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

Optimising DevOps

3) Pre-empting Failure

Page 2: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

Application Performance Management

(APM)

Page 3: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

APM Defined

“In the fields of information technology and systems management, application performance management (APM), is the monitoring and managing of performance and availability of software applications. APM strives to detect and diagnose application performance problems to maintain an expected level of service”

http://en.wikipedia.org/wiki/Application_Performance_Management

Page 4: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

APM Defined

“In the fields of information technology and systems management, application performance management (APM), is the monitoring and managing of performance and availability of software applications. APM strives to detect and diagnose application performance problems to maintain an expected level of service”

http://en.wikipedia.org/wiki/Application_Performance_Management

Page 5: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

APM Defined

“In the fields of information technology and systems management, application performance management (APM), is the monitoring and managing of performance and availability of software applications. APM strives to detect and diagnose application performance problems to maintain an expected level of service”

http://en.wikipedia.org/wiki/Application_Performance_Management

Page 6: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

“5 Dimensions of APM*”

1. End user experience monitoring - (active and passive)

2. Application runtime architecture discovery and modelling

3. User-defined transaction profiling (also called business transaction management)

4. Application component monitoring5. Reporting & Analytics

*According to Gartner

Page 7: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

15 Reasons why you need APM

1. “THE AGE OF THE CUSTOMER”

2. E-COMMERCE3. NEW DEVELOPMENT

METHODS – AGILE AND SCRUM

4. FASTER DEVELOPMENT CYCLES

5. REDUCED IT BUDGETS AND RESOURCES

6. INCREASED NUMBER OF APPLICATIONS

7. DISTRIBUTED APPLICATIONS

8. CLOUD9. PAAS10. VIRTUALIZATION11. SOFTWARE DEFINED

DATA CENTERS12. MOBILITY13. BYOD14. INCREASED STRAIN ON

THE NETWORK15. FASTER NETWORK

SPEEDS

http://apmdigest.com/15-reasons-why-you-need-apm-in-2014-1 http://apmdigest.com/15-reasons-why-you-need-apm-in-

2014-1

Page 8: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

15 Reasons why you need APM

1. “THE AGE OF THE CUSTOMER”

2. E-COMMERCE3. NEW DEVELOPMENT

METHODS – AGILE AND SCRUM

4. FASTER DEVELOPMENT CYCLES

5. REDUCED IT BUDGETS AND RESOURCES

6. INCREASED NUMBER OF APPLICATIONS

7. DISTRIBUTED APPLICATIONS

8. CLOUD9. PAAS10. VIRTUALIZATION11. SOFTWARE DEFINED

DATA CENTERS12. MOBILITY13. BYOD14. INCREASED STRAIN ON

THE NETWORK15. FASTER NETWORK

SPEEDS

http://apmdigest.com/15-reasons-why-you-need-apm-in-2014-1 http://apmdigest.com/15-reasons-why-you-need-apm-in-

2014-1

Page 9: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

15 Reasons why you need APM

1. “THE AGE OF THE CUSTOMER”

2. E-COMMERCE3. NEW DEVELOPMENT

METHODS – AGILE AND SCRUM

4. FASTER DEVELOPMENT CYCLES

5. REDUCED IT BUDGETS AND RESOURCES

6. INCREASED NUMBER OF APPLICATIONS

7. DISTRIBUTED APPLICATIONS

8. CLOUD9. PAAS10. VIRTUALIZATION11. SOFTWARE DEFINED

DATA CENTERS12. MOBILITY13. BYOD14. INCREASED STRAIN ON

THE NETWORK15. FASTER NETWORK

SPEEDS

http://apmdigest.com/15-reasons-why-you-need-apm-in-2014-1 http://apmdigest.com/15-reasons-why-you-need-apm-in-

2014-1

Page 10: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

15 Reasons why you need APM

1. “THE AGE OF THE CUSTOMER”

2. E-COMMERCE3. NEW DEVELOPMENT

METHODS – AGILE AND SCRUM

4. FASTER DEVELOPMENT CYCLES

5. REDUCED IT BUDGETS AND RESOURCES

6. INCREASED NUMBER OF APPLICATIONS

7. DISTRIBUTED APPLICATIONS

8. CLOUD9. PAAS10. VIRTUALIZATION11. SOFTWARE DEFINED

DATA CENTERS12. MOBILITY13. BYOD14. INCREASED STRAIN ON

THE NETWORK15. FASTER NETWORK

SPEEDS

http://apmdigest.com/15-reasons-why-you-need-apm-in-2014-1 http://apmdigest.com/15-reasons-why-you-need-apm-in-

2014-1

Page 11: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

Actually - 1 Reason

1. Avoid bad press!

Page 12: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

Page 13: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

CA

QuestHP

OpTier

Opnet

IBM

Compuware

Oracle

MicrosoftSL

Inetco

NetScout

eG InnovationsProgress

ASG

IderaVisual networks

Info vista

Network Instruments

Knoa

Aternity

Coradient

CorrelsenseNastel

dynaTracePrecise

Arctures Technologies

BMC

Managed Engine

New RelicAppDynamics

2011Riverbed

OpTier

2012

AppNeta

Dell

2013

Gartner APM Magic Quadrant

Page 14: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

Page 15: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

Page 16: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

Page 17: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

Page 18: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

Page 19: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

Page 20: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

Page 21: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

Pre-Empting Failure

Page 22: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

Pre-emptive analytics• Provides additional analytics on

application performance and potential/actual issues before they effect the user experience

• Identifies root cause issues in deployed application components to facilitate DEV fixes/re-factoring and OPS deployment optimisation

• Provides visual indicators of traffic flow and response times across the application deployment that can drive infrastructure and service optimisation

Page 23: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

Pro-active failure avoidance

• APM supporting DevOps….– For deployment

automation/orchestration:• New releases of refactored application

components to cope with predicted issues• Versioned “last known good” components in

the event of potential, actual or planned outage

– For scalability:• Triggering additional instances of deployed

infrastructure components on-demand• Reactive to traffic growth predictions or

patterns

Page 24: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

Moving from the blame game…

Ops DevQA

Page 25: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

To the (pre-emptive) fix-It game

Ops

DevQA

Page 26: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

APM as a organisation heartbeat

• APM Provides a unified view of the situation that the “3 amigos” (Dev, Ops & QA) cannot dispute

• APM-driven activities fit nicely with Agile delivery approaches…..and can be measured and re-measured

• APM is THE DevOps dashboard• Keep the heart going!

Page 27: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

The Numbers

Page 28: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

APM for business value

• What is the cost of an outage?– Revenue loss– Reputational damage– Customer service costs

• What is the cost of slow performance?– Revenue*/minute correlates to response

time– Abandoned transactions, dissatisfied

customers*Substitute your measure here

Page 29: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

The “ROI” QuestionINCIDENT REDUCTION• Reduced mean time to resolve (MTTR)• Reduction in high impact outages• Reduction in number (and severity) of support tickets

MAXIMISED REVENUE OPPORTUNITY• Maximum uptime• Efficient business transactions• Applications engineered for response times

INCREASED CUSTOMER SATISFACTION• Increased reliability (and performance) across device and

browser types• Applications and infrastructure focussed on the customer

experience

Page 30: Optimising DevOps: Pre-empting Failure

www.ranger4.com

DevOpstastic

Panel Discussion