Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on Incident Management, On-Call, Incident Response and related technologies.

PagerDuty Announces New Automation Enhancements That Simplify Operations Across Distributed and Zero Trust Environments

Be sure to register for the launch webinar on Thursday, March 30th to learn more about the latest release from the PagerDuty Operations Cloud. Rundeck by PagerDuty has long helped organizations bridge operational silos and automate away IT tasks so teams can focus more time on building and less time putting out fires. And while this mission still rings true today, our vision is to extend this reality and revolutionize all operations while continuing to build trust.

What Is MTTR?

Mean Time To Repair, or MTTR, is a critical metric in IT incident management that measures the average time it takes to fix a system failure. The meaning of MTTR can be understood as the average duration needed for an IT team to recover from an incident. It is a fundamental metric for IT teams to track and analyze their efficiency in resolving incidents.

Bring Order to On-call Chaos With Splunk Incident Intelligence

In today’s turbulent times, companies big and small are being pushed to do more with less. Budgets are getting tighter and companies are being pressured to serve customers who demand 24/7 availability from their applications and services. To meet these demands and remain competitive, enterprises are adopting cloud-first strategies and developing applications with microservice architectures.

Splunk Incident Intelligence Demo

Splunk Incident Intelligence is a team-based incident response solution that connects the right on-call staff to the actionable data they need to diagnose, remediate and restore services quickly. Integrated with the Splunk Observability Cloud portfolio of products, it helps you unify incident response, streamline your on-call and ultimately resolve incidents faster.
Sponsored Post

The Evolution of Incident Management from On-Call to SRE

Incident Management has evolved considerably over the last couple of decades. Traditionally having been limited to just an on-call team and an alerting system, today it has evolved to include automated Incident Response combined with a complex set of SRE workflows.

How FireHydrant handled the SVB banking crisis

On Thursday, March 9, 2023, something was afoot at our primary bank, SVB. By Friday, March 10, 2023, messages from our investors helped us quickly understand that FireHydrant needed to maneuver through a complex incident that was unfolding. Operational incidents are incidents like every other.

Automatically Create Incidents from Alerts with Alert Routing

Shouldn’t your alerts be doing more of the work for you? A noisy channel with every alert from hundreds of monitors and microservices is a chaotic place to actually find the incidents that are impacting your customers. And it still requires a heck of a lot of human intervention. We think it’s time for something better. Today we’re releasing Alert Routing: the next phase of worry-free automation from FireHydrant.

How to define roles for your incident response team

Agility matters in incident response, and the easiest way to spring into action is by having a well-defined team in place ahead of time. The right people in the right roles will help you respond to and resolve incidents more quickly and efficiently. In fact, we found in the Incident Benchmark Report that incidents with roles assigned had a 42% lower mean time to resolution than those that didn’t. But what roles do you need to fill?