Resolving an incident can be a complex process that takes a lot of time and many people. According to the 2014 State of On-Call Report, most teams report that it takes 10-30 minutes to resolve an incident and on average, 5 people are needed to help with resolution.
Join Jason Hand, DevOps evangelist, and Michael Ansel, from Box, as they explain what ChatOps is and how it can help different teams in your organization. You'll learn tips to get started, tools needed and emerging best practices around the topic.
In today's modern infrastructure, it's imperative to have situational knowledge about what's going on...the good, the bad, everything. The DevOps movement has taught us that monitoring is a key component of adopting the best practices of highly efficient software delivery teams. These metrics are not only useful as context during incident management but also to analyze once an outage has been resolved.
DevOps represents cultural change. Whether it's the change of resistant engineers that don't want to be on-call or the change of Operations teams to have more empathy towards their counterparts writing code, to the willingness of executives to embrace a culture of automation, measurement and sharing.
The teams and organizations that are leading the DevOps movement have turned to their chat client to provide a new interface. We are already in chat all day, sharing, collaborating, and conversing on what is taking place across all business units and projects. By moving tools and command line functionality into chat, we are able to create greater situational awareness and tribal knowledge.
Need some help getting started with ChatOps? In this webinar we talk about the benefits to implementing ChatOps within your team and how it can decrease the time it takes to deploy code, mitigate infrastructure incidents, and act as a learning tool.
Following up an incident, outage, or even a successful deployment with a post-mortem isn't a new concept. It's easy to understand the benefits of sharing, analyzing, and understanding what went well and what didn't. In many cases, individuals blame others, or worse, themselves for actions that may have led to an outage.
Real time network monitoring tools help you respond to danger… but in our 2014 State of On-Call Report, 63% of IT pros said alert fatigue is an issue and 64% believe that up to a quarter of all alerts are false alarms!
Join us as we talk about the results of our second-annual State of On-call Survey. We got over 600 responses and people dished on all aspects of being on-call: from team set-up to post-mortems to what tools are best for incident remediation. Find out more...