Find the Latest in DevOps & More in Our Learning Library Start Here.
December 19, 2019
“I already have [insert your incident management tool of choice], do I really need incident response software?”
The answer is a resounding YES.
The shift from waterfall to CI/CD means faster, more frequent delivery. But increased ships to production means more bugs, more critical incidents and more downtime. Old school incident management just isn’t enough.
Service management expert, Jason Odden of Splunk, and incident response expert, Bill Emmett of Splunk + VictorOps are teaming up to show you how high-performing teams join incident management with incident response to improve mean time to resolve and reduce system downtime — or prevent it altogether. You’ll learn:
Why incident management isn’t enough: Think beyond the service desk ticket for rapid acknowledgment and resolution of critical incidents
The right approach for the right people: Give developers the right processes and tools to support incident resolution
The role of the “ambulance” vs. the “hospital”: Understanding the role of an ITSM tool like ServiceNow versus an incident response tool like VictorOps
How to bridge the gap: Operations, development and support all work in different tools — learn practical strategies for meeting them where they are
How to Succeed in Machine Learning Without Really Trying
Use Machine Learning to Empower Teams and Make On-Call Suck Less Machine Learning is more than a buzzword. Proper ML empowers teams instead of replaces...Download Now
Death to Downtime
How to Quantify and Mitigate the True Costs of Downtime: Gartner estimates the average cost of downtime at $5,600 per minute, which multiplies to over...Download Now
How to Make On-Call Suck Less
5 Quick Wins for a More Humane On-Call Experience: If on-call duties are a major source of dread, or if you have the sneaking suspicion...Download Now