Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Optimising DevOps: Pre-empting Failure

1,164 views

Published on

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.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Optimising DevOps: Pre-empting Failure

  1. 1. Optimising DevOps 3) Pre-empting Failure www.ranger4.com DevOpstastic
  2. 2. Application Performance Management (APM) www.ranger4.com DevOpstastic
  3. 3. 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 www.ranger4.com DevOpstastic
  4. 4. 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 www.ranger4.com DevOpstastic
  5. 5. 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 www.ranger4.com DevOpstastic
  6. 6. “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 monitoring 5. Reporting & Analytics *According to Gartner  www.ranger4.com DevOpstastic
  7. 7. 15 Reasons why you need APM http://apmdigest.com/15-reasons-why-you-need-apm-in-2014-1 http://apmdigest.com/15-reasons-why-you-need-apm-in-2014-1 1. “THE AGE OF THE CUSTOMER” 2. E-COMMERCE 3. 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. CLOUD 9. PAAS 10. VIRTUALIZATION 11. SOFTWARE DEFINED DATA CENTERS 12. MOBILITY 13. BYOD 14. INCREASED STRAIN ON THE NETWORK 15. FASTER NETWORK SPEEDS www.ranger4.com DevOpstastic
  8. 8. 15 Reasons why you need APM http://apmdigest.com/15-reasons-why-you-need-apm-in-2014-1 http://apmdigest.com/15-reasons-why-you-need-apm-in-2014-1 1. “THE AGE OF THE CUSTOMER” 2. E-COMMERCE 3. 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. CLOUD 9. PAAS 10. VIRTUALIZATION 11. SOFTWARE DEFINED DATA CENTERS 12. MOBILITY 13. BYOD 14. INCREASED STRAIN ON THE NETWORK 15. FASTER NETWORK SPEEDS www.ranger4.com DevOpstastic
  9. 9. 15 Reasons why you need APM http://apmdigest.com/15-reasons-why-you-need-apm-in-2014-1 http://apmdigest.com/15-reasons-why-you-need-apm-in-2014-1 1. “THE AGE OF THE CUSTOMER” 2. E-COMMERCE 3. 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. CLOUD 9. PAAS 10. VIRTUALIZATION 11. SOFTWARE DEFINED DATA CENTERS 12. MOBILITY 13. BYOD 14. INCREASED STRAIN ON THE NETWORK 15. FASTER NETWORK SPEEDS www.ranger4.com DevOpstastic
  10. 10. 15 Reasons why you need APM http://apmdigest.com/15-reasons-why-you-need-apm-in-2014-1 http://apmdigest.com/15-reasons-why-you-need-apm-in-2014-1 1. “THE AGE OF THE CUSTOMER” 2. E-COMMERCE 3. 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. CLOUD 9. PAAS 10. VIRTUALIZATION 11. SOFTWARE DEFINED DATA CENTERS 12. MOBILITY 13. BYOD 14. INCREASED STRAIN ON THE NETWORK 15. FASTER NETWORK SPEEDS www.ranger4.com DevOpstastic
  11. 11. Actually - 1 Reason 1. Avoid bad press! www.ranger4.com DevOpstastic
  12. 12. www.ranger4.com DevOpstastic
  13. 13. CA IBM Quest HP 2011 Riverbed 2012 2013 Compuware AppDynamics OpTier Opnet Oracle Microsoft SL BMC Inetco Dell NetScout New Relic Nastel eG Innovations Progress AppNeta Managed Engine Idera Visual networks ASG Network Instruments Info vista Correlsense Coradient Knoa Aternity Precise Arctures Technologies OpTier Gartner APM Magic Quadrant www.ranger4.com DevOpstastic
  14. 14. www.ranger4.com DevOpstastic
  15. 15. www.ranger4.com DevOpstastic
  16. 16. www.ranger4.com DevOpstastic
  17. 17. www.ranger4.com DevOpstastic
  18. 18. www.ranger4.com DevOpstastic
  19. 19. www.ranger4.com DevOpstastic
  20. 20. www.ranger4.com DevOpstastic
  21. 21. Pre-Empting Failure www.ranger4.com DevOpstastic
  22. 22. 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 www.ranger4.com DevOpstastic
  23. 23. 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 www.ranger4.com DevOpstastic
  24. 24. Moving from the blame game… QA Ops Dev www.ranger4.com DevOpstastic
  25. 25. To the (pre-emptive) fix-It game Ops Dev QA www.ranger4.com DevOpstastic
  26. 26. 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! www.ranger4.com DevOpstastic
  27. 27. The Numbers www.ranger4.com DevOpstastic
  28. 28. 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  www.ranger4.com DevOpstastic
  29. 29. The “ROI” Question INCIDENT 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 www.ranger4.com DevOpstastic
  30. 30. Panel Discussion www.ranger4.com DevOpstastic

×