From spam to value: Holistic APM and intelligent incident management
summary
The talk explains how to get full value from a monitoring/observability system by designing an optimal APM setup and managing alert floods. It covers which data types form the foundation of a modern observability platform and how to build a holistic, sustainable incident-management process to turn noisy alerts into actionable value.
AI-written summary · about
chapters (33)
- 0:00Welcome
- 1:47APM basics
- 3:12Why observability
- 8:14Monitoring vs observability
- 10:22Observability pillars
- 13:30Live demo setup
- 15:39Dashboards and metrics
- 16:45System and JPM metrics
- 18:30HTTP errors
- 19:54Logs and trace IDs
- 20:58Traces deep dive
- 22:01Alerts and escalation
- 23:11Turning data into value
- 24:37Incident basics
- 26:00Incident vs problem
- 27:44Incident phases
- 29:53Monitoring as early warning
- 31:16Alert challenges
- 34:09Incident best practices
- 35:33Process and tools
- 39:45SPOC and tools
- 41:11Tool requirements
- 44:25Service prep and wrap-up
- 45:28Service levels and playbooks
- 46:54Runbooks and knowledge
- 47:56Root cause and postmortems
- 49:23Trust culture
- 51:08Alert prioritization
- 52:34Notification rules
- 53:15Alert reviews
- 54:59Why APM and ICM
- 58:36Summary
- 59:23Q&A
related talks
42mUnified observability, AIOps, and incident response for AWS
39mPanel Discussion: Application Monitoring
29mObservability; a gentle introduction
52mHolistic Monitoring
27mAlert Fatigue to Action: Observability as the Backbone of Practical AIOps with OpenSearch
33mBeyond Monitoring: The Rise of Observability Platform
46mObservability best practices for hybrid environments
48mDevOps Transformation: Introducing Incident Management and Maximizing Monitoring Value