Our mission is to unleash the potential of all teams by harnessing the power of collaboration tools and practices. This is particularly true for teams practicing DevOps, which is all about unlocking collaboration between development, IT operations, and business teams. However, this increased collaboration can come at a cost to developers.
Get stories like this in your inbox During an IT incident, every second counts – but the first few minutes are the most critical. Teams who can rapidly spin up the right tools and processes have the best shot at fast resolution. And of course, many teams rely on chat tools to collaborate and communicate during incidents. So we’re excited to announce our new Slack app for Opsgenie Incidents.
A lot of teams are asking us about how to do incident management when you’re suddenly remote. We understand. Going remote can be scary, and few things are scarier than having a service outage you aren’t prepared for. Nobody wants to be in a situation where an important service going down and the engineer who can help isn’t answering on Slack. And if your company isn’t used to working remotely, it can be harder than ever to be on the same page during an incident.
Setting and tracking key performance indicators based on the right data can help incident management teams reduce the impact of incidents and strengthen the business. But what exactly is the right data? That can be a deceptively tricky question. Incidents are complex, and no two are exactly the same – and your KPIs must reflect this complexity.