The latest News and Information on Incident Management, On-Call, Incident Response and related technologies.
Earlier this month, many areas of the internet experienced a major incident caused by a router misconfiguration within a highly used service provider. This led to cascading service failures, causing widespread outages and disruptions for several well-known SaaS organizations. When the outage occurred, our teams at PagerDuty immediately noticed a global spike in events and incidents.
We’re excited to announce a new set of product updates and enhancements to the PagerDuty platform! PagerDuty partners with organizations to help teams create efficiencies across IT organizations and protect customer relationships. These updates will help further improve your team’s ability to manage and reduce noise, automate critical response workflows, and quickly mobilize a response in order to mitigate disruptions across your digital operations when seconds matter.
Ask any IT Ops practitioner what the first question they ask is when joining an emergency bridge call, and you’ll get the same answer: “What changed?” Our customers report that changes in their IT environments cause 60% to 90% of the incidents they see. Yet for some reason enterprises still find it difficult to deal with changes and correlate them to the IT incidents they may have caused.
Incident response doesn’t only happen in Slack, so today we’re happy to announce our integration with Zoom to create incident bridges automatically. Using the power of FireHydrant Runbooks, a Zoom meeting can be added with fully customizable titles and agendas based on your incident details. Let’s dive into how it works.
Solving incidents is hard. Depending on your current situation, you may also be losing a lot of time figuring out what notifications constitute an incident. This results in more and more lost time as every notification must be triaged as a potential incident before you can proceed to move to resolve or disregard (as a non-incident). All this may sound very cumbersome, but the fastest way to improve is to learn and define what incidents are. And you’re in luck!
Your enterprise likely has a network operations center (NOC) and a security operations center (SOC), both of which play an important role in your day-to-day operations. But, what differentiates your NOC from your SOC? To find out, let’s answer some of the key questions surrounding NOC vs.SOC.
