Why Automated Remediation?
Redmonk Analyst and Steve O'Grady sits down with Anurag Gupta to define automated remediation
Why does production operations need a tool to automate incidents away? Does this replace performing a root cause analysis? Can you really rely on machines to handle production automations, or will that just make things worse?
In this webinar, Redmonk Analyst, Steve O'Grady sits down with Anurag Gupta to define automated remediation, discuss when it's useful, and get into Anurag's experience running databases and analytics at AWS that led to starting Shoreline.
Automated remediation is no substitute for root cause analysis. But, you need to alleviate the immediate problem faced by your customers while you schedule root cause repair by your dev team. If you go to the ER with a heart attack, it’s the wrong time to hear about your diet or high cholesterol.
We've automated testing, configuration, and deployment - we also need to automate repetitive incidents, and we need tools that make makes root-causing transient issues much easier by capturing all the debugging information whenever a bad condition is observed.
What you'll learn
- Why it's just as important to automate production incident remediation as it was to automate software development, testing, and deployment.
- Why incident automation and observability tools are insufficient to let on-call engineers sleep at night.
- Why automated remediation doesn't already exist.
- How to most enterprises are approaching the journey of moving toward automating incident response in production operations.