Operations | Monitoring | ITSM | DevOps | Cloud

From managing issues and resources to keeping customers updated, resolving an incident requires a level of multi-tasking that can be overwhelming for even the most efficient of teams. Automating your processes reduces the time needed to diagnose, mitigate, and resolve incidents, and simplifies communication throughout an incident's lifecycle.

Join us for a deep dive into how incident.io is leveraging AI to build an intelligent incident investigator. Our guests, Ed and Lawrence, share insights on building AI-powered investigations that help teams to leverage huge amounts of data and signals to respond faster and more effectively.

While on-call groups are the perfect solution when you need the right person at the right time to solve a specific problem, there are times when you need to notify everybody all at once. Whether you’re sending an informational message about some upcoming maintenance or an emergency notification about an issue that could affect an entire office, broadcast groups enable you to notify large groups of people at the same time. They can contain more members than on-call groups because there’s no rotation or escalation schedule to work out.

In the high-stakes world of fleet management, reliability isn’t a nice-to-have—it’s a necessity. That’s why Motive has invested heavily in tools and processes to ensure its systems run smoothly for over 150,000 customers and more than a million vehicles. At the center of its ability to deliver 99.99% uptime at scale is Rootly.

Last year, over 89% of companies claimed to have adopted platform engineering. And, in the past month, LLMs have been disrupting how we think about software development. In this context, Kaspar, asks if the role of Site Reliability Engineers is being obsolete as we know it. Kaspar argues that while SREs aren’t going anywhere, their responsibilities are evolving—fast. We talk about.

Dive into the world of Incident Management with our latest video! We'll explore the essential concept of Incident Severity Levels and why they're crucial for any organization.

The shift to zero trust security requires a model that is identity-based, centrally managed, widely encrypted, and always authenticated and authorized. PagerDuty Runbook Automation enables users to automate, orchestrate, and accelerate issue resolution with best practice security guardrails, reducing human error and saving time. Host: Sid Verma (Senior Developer Advocate at PagerDuty) Guests: Christopher Hills (Chief Security Strategist at BeyondTrust); Jake Cohen (Senior Product Manager at PagerDuty)

Traditional MTTx metrics have long been the go-to measure for incident management effectiveness, but they often fail to provide a full picture or drive meaningful improvements. We analyzed data from over 100,000 incidents to develop new industry benchmark metrics that better define what "good" incident management looks like.

When an incident occurs, teams often perform a known set of steps in a specific order to help identify and triage the incident. For Base and Advanced plan users, the Incidents menu includes a Task Lists section where teams can build out priority lists for different incident types or use cases. For example, a list of failover tasks, or the tasks required to perform a deployment rollback. With task lists, Incident Commanders can be sure that resolvers know exactly what needs to be done to quickly resolve incidents.

Join us to hear and see what's new in Runbook Automation and Rundeck v5.10!

Dan Slimmon is an incident management veteran who's worked at Etsy, HashiCorp, and now leads consulting and training on pragmatic, non-bureaucratic incident response. In this episode, Dan shares his philosophy on "scientific incident response," the importance of hypothesis-driven troubleshooting, and why incidents should be seen as normal in complex systems.

Join us for an informal 1-hour virtual event where the open-source Rundeck by PagerDuty community comes together to share automation stories and use cases. Whether you're new to Rundeck or looking to elevate your automation game, this meetup is packed with valuable takeaways for everyone! CERN Orchestrates with Rundeck.

With the mobile alerting app from SIGNL4, you can manage your alarms from anywhere. Receive real-time push notifications directly on your smartphone. Respond to incidents and communicate directly with your team within the app. Resolve issues quickly and effectively or handle urgent service requests – no matter where you are.

Just because Flow Designer is a simple, visual workflow builder doesn’t mean that the flows you build have to be simple, too. In fact, flows can get very complex very quickly, especially as you connect more tools and create your toolchain. To help you build out and handle more complex logic and multiple paths, the Condition step automatically changes a flow’s path based on the value of almost any property in your flow. You can use the Condition step to compare values using AND/OR logic and a range of conditional operators to determine the appropriate path. And if the values don’t match, never fear!

Mariano, Staff Product Manager at Vercel, explains why serverless architectures are hitting unexpected limits—they’re too fast. The industry has spent millions optimizing serverless for speed, but AI workloads are changing the game. In the AI realm, slower execution often leads to better results. The challenge? Paying for all that idle compute time while waiting for AI responses.

Join us for this webinar as we explore how our newly launched Sumo Logic Mo Copilot redefines incident management with the power of AI. We'll examine the limitations of traditional troubleshooting methods and why they fall short in today’s fast-paced environments. Discover how Mo Copilot leverages advanced machine learning and automation to streamline root cause analysis and reduce mean time to resolution (MTTR). We'll also showcase a live demonstration and highlight how Mo Copilot integrates into your workflow, transforming how you manage operational reliability.

What is most important for efficient incident management? Effective incident management starts before incidents occur. Ideally, alerts should trigger preemptively to prevent outages or fire immediately when issues arise, minimizing downtime and resolution time.

Although not all incidents are the same, resolvers often need similar resources or follow standard processes when responding to them. To save valuable time and effort, teams who frequently reference or attach the same files when sending incident notifications can use the xMatters Document Library to store everything in one place. You can easily add and organize files such as screenshots, maps, or response plans and attach them to incidents from within the library or directly on the incident console. For sensitive documents, set permissions so only certain roles can access, modify, or delete them.