When an incident occurs, do you shudder when either you or your team proceed to open multiple browser tabs for each of your monitoring tools? This is the picture painted by the “swivel-chair” effect, context-switching between tools to gather information needed to determine a path of resolution.

In a survey conducted at Microsoft Ignite 2018 in Orlando, Florida, Derdack investigated the state of IT alerting solutions among businesses. The survey is based on 368 participants, randomly selected among IT professionals visiting the expo showfloor. The survey revealed if and if yes, which IT alerting solutions (ITSA / “IT Service Alerting”) businesses use to support their IT operations and to respond faster to major and critical IT incidents.

IT Operations, DevOps, and Developer teams count on PagerDuty’s 300+ integrations to power their end-to-end real-time digital operations, no matter which tool stack they use. Because PagerDuty’s customers span all sizes, industries, and digital maturity levels, our product team is constantly talking to customers about which tools they use for needs like communications, APM, and IT Service Management (ITSM).

When incidents happen, many organizations have formalized processes for dealing with the issue. OpsGenie helps organizations manage their incident response processes smoothly from one single place. Now, as an addition to our Incident Management features, we are happy to announce Incident Response Roles!

Do any of these sound familiar? One of your best engineers just put in notice that they are taking a job elsewhere because the on-call load while working for you is destroying their personal life—but you honestly thought things were fine.

There are two common approaches to incident response: qualitative and quantitative. Each approach has its pros and cons. Meanwhile, an enterprise’s decision to take a qualitative or quantitative approach to incident response could have far-flung effects on the business, its employees and its customers.