The incident response industry is anything but static, and it is often said that the key to staying ahead is staying informed. But that’s easier said than done. Faced with the increasing sophistication of cyber attacks and the growing complexity of IT architectures, we often drown in our daily slew of tickets and alerts, with no time left to spare.
Modern hybrid, multi-cloud, and cloud native environments have created increased management complexity for enterprise IT teams. Dynamic and distributed applications, infrastructure and business-critical services are constantly generating more data in the form of metrics, events, and alerts.
We’re launching a new feature today that allows anyone in your organization to kick off your incident response process with an appropriate severity level attached from Slack. Often people are afraid to open an incident or even share that they’re aware of something going wrong with your applications. When everything is important, nothing is important; users frequently overestimate the impact of an incident and assign an inappropriately high severity level.
Cloud adoption continues to increase, and although Forbes projects that 83% of enterprise workloads will be in the cloud by 2020, that leaves approximately 17% still on-premises. For many organizations, a hybrid approach to infrastructure strikes the right balance. Regardless, whether running cloud, on-prem, or hybrid environments, IT teams must stay aware and in control during incidents and service disruptions. This need was the reason we built Edge Connector for Opsgenie.
This week at re:Inforce in Boston, the AWS team showed off its Security Hub service—a powerful service that provides SecOps teams a comprehensive view of their high-priority security alerts and compliance status across their AWS accounts. We’re excited to join AWS at re:Inforce this week as a Security Hub partner, where we’ll show users how PagerDuty and AWS Security Hub work together to provide real-time SecOps to any team using AWS.
We’re pleased to come home from DattoCon19 with memorable experiences. It was a well-curated conference, striking a fine balance between emerging MSP trends, informative sessions, networking and of course, entertainment. Here are my top takeaways from the event.
On June 20 we have released the 3rd update for EnterpriseAlert 2019. Don’t get confused by the version number, 8.2.0 would better be 8.3.0, but that’s the way it is. Here is a very short EA 2019 release history for CY 2019.
The PagerDuty Incident Response Process is a detailed document that provides a framework for how to structure your incident response process. But sometimes it helps to understand how these seemingly abstract concepts play out during real-world scenarios. You can now hear an incident call recording that’s based on a real PagerDuty incident. Due to the nature of incident response practices, the process guide we publish is filled with very explicit details regarding a variety of situations.
While there are some very good sources out there on how to manage a critical incident, Google also wrote a chapter on incident management in their book, “Site Reliability Engineering”. In this chapter, the folks at Google present their approach to a well-designed critical incident management process.
This month, we are excited to announce a new set of product capabilities and enhancements designed to ensure that teams can work in real time, all the time, wherever they are. Whether they’re on-the-go with their mobile devices or at their desks on a typical work day, we will continue to innovate without sacrificing ease-of-use and adoption.
