Uploaded byMeasureWorks
MeasureWorks - Performance Labs - Why Observability Matters!
The document discusses the importance of observability as a management strategy for identifying key issues in operations and improving web performance. It outlines the four pillars of web performance—reachability, availability, reliability, and consistency—and emphasizes the value of understanding normal system behavior to predict downtime and manage performance effectively. By implementing observability, organizations can enhance their ability to monitor systems, enabling smarter and faster operations.
In this document
Powered by AI
Introduces observability as a management strategy for prioritizing key operational issues.
Discusses various aspects of performance including waits and customer service perception.Identifies four pillars of web performance: Reachability, Availability, Reliability, and Performance.
Talks about challenges in performance, such as failures, budgets, incident alerts, and service impact.
Emphasizes the importance of dashboards and typical downtime patterns on operational performance.
Discusses the ability to predict downtime using behavior patterns and alerts for performance monitoring.
Focuses on user experience degradation leading to errors and the significance of recognizing normal behavior.
Explores system thinking and the holistic approach needed for effective observability, including implementation.
Wraps up the presentation and opens the floor for questions.
More Related Content
Similar to MeasureWorks - Performance Labs - Why Observability Matters!
MeasureWorks - Performance Labs - Why Observability Matters!
- 1. Why observability matters! JeroenTjepkema Product Director @ MeasureWorks
- 2. Observability: Observability is amanagement strategy focused on keeping the most relevant, important and core issues at or near the top of an operations process flow.
- 3.
- 9.
- 10.
- 11.
- 12.
- 13. “Both of fl ine andonline we associate bad performance with poor customer service”
- 14. Reachability Availability Reliability CanI get there? Is it working? Performance Fast or Slow? Working consistent? 4 pillars of web performance
- 15. Reachability Availability Reliability CanI get there? Is it working? Performance Fast or Slow? Working consistent? when the delivery of quality is noticeable but does but does not influence the user’s preference of one service over another. This allows you a position to win from you competitors. 4 pillars of web performance Time neutralisation:
- 16. The reality is,things fail…
- 17. Performance Budgets IncidentAlerts Service Impact Setting thresholds?
- 18.
- 19. …did we misssomething?
- 21. 0 15 30 45 60 0 5 1015 20 25 30 35 40 45 50 55 60 # pageviews Min/Hour Typical downtime pattern
- 22. 0 15 30 45 60 0 5 1015 20 25 30 35 40 45 50 55 60 # pageviews Min/Hour Regular operations Typical downtime pattern
- 23. 0 15 30 45 60 0 5 1015 20 25 30 35 40 45 50 55 60 # pageviews Min/Hour Regular operations Alerts? Typical downtime pattern
- 24. 0 15 30 45 60 0 5 1015 20 25 30 35 40 45 50 55 60 # pageviews Min/Hour Regular operations Alerts? Downtime Typical downtime pattern
- 25. 2 examples Q: Canwe predict downtime?
- 26. 0 15 30 45 60 0 5 1015 20 25 30 35 40 45 50 55 60 # pageviews Min/Hour Example downtime pattern Regular operations Alerts? Downtime This is where we want to be!
- 27. 0 15 30 45 60 0 5 1015 20 25 30 35 40 45 50 55 60 # pageviews Min/Hour Example downtime pattern Regular operations Alerts? Downtime This is where we want to be! News
- 29. c sites for 4months: Behaviour patterns are a leading indicator to alerts
- 30. 0 15 30 45 60 0 5 1015 20 25 30 35 40 45 50 55 60 # pageviews Min/Hour Example downtime pattern Time period in which we can detect a persistent change in pattern per type of monitoring Social Alerting Change in click behavior Performance alerting
- 31. Remember: 85-90% of allerrors are caused by degradation in user experience…
- 32. Another way tolook at it
- 33.
- 34.
- 35. Not understanding whatnormal behavior looks like makes us do stupid things...
- 36.
- 37. By measuring behaviourof a system turns silos into noise and turns causation into likelihood
- 38. Predict performance? Understand whatnormal is
- 39.
- 40. Enter: System Thinking Enter:System Thinking making sense of the complexity of your environment by looking at it in terms of whole rather than by splitting it down into silos
- 41. 41 Internet DB Load balancer Web serverApp server Digital Touchpoint Datacenter Application Delivery Chain
- 42. Multi-vendor Management (Multi) Cloud providers 42 Internet DB Load balancer Web serverApp server Digital Touchpoint Datacenter Application Delivery Chain External data providers CDN Delivery Quality
- 43. Multi-vendor Management (Multi) Cloud providers 43 Internet DB Load balancer Web serverApp server Digital Touchpoint Datacenter 3d parties Application Delivery Chain External data providers CDN Delivery Quality Marketing Efforts
- 44. Multi-vendor Management (Multi) Cloud providers 44 Internet DB Load balancer Web serverApp server Digital Touchpoint Datacenter 3d parties Application Delivery Chain External data providers CDN Performance Marketing campaigns Autonomous growth Delivery Quality Marketing Efforts Traffic
- 45. Multi-vendor Management (Multi) Cloud providers 45 Internet DB Load balancer Web serverApp server Digital Touchpoint Datacenter 3d parties Application Delivery Chain External data providers CDN Performance Marketing campaigns Autonomous growth Delivery Quality Marketing Efforts Traffic Span of control?
- 46. At the sametime we want to speed up cycle time…
- 48.
- 49. Observability: Observability is amanagement strategy focused on keeping the most relevant, important and core issues at or near the top of an operations process flow.
- 50.
- 51.
- 52. Quality Gates Automated Performance Teststaging environment
- 53.
- 54.
- 55. Shift left, ShiftRight? Work smarter, faster…
- 56. Thanks! More questions? M:jtjepkema@measureworks.nl T: @jeroentjepkema W: www.measureworks.nl