Operations | Monitoring | ITSM | DevOps | Cloud

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

ilert now supports a native WhaTap integration

ilert now supports a native WhaTap integration, connecting AI-native observability with AI-first incident management in a seamless workflow. This integration allows DevOps, SRE, and IT teams to move instantly from detection to resolution – cutting through alert noise, improving coordination, and dramatically reducing MTTR in even the most complex IT environments.

How to Create and Manage Incidents in Uptime.com

Learn how to create and manage incidents on your Uptime.com Status Page to keep your subscribers informed about service disruptions and maintenance events in real-time. In this tutorial, we'll cover understanding incident statuses (Investigating, Identified, Monitoring, Resolved, and more), three ways to create a new incident, configuring incident details and timelines, adding updates with Markdown formatting, managing and editing incidents, notifying Status Page subscribers, and using the REST API for incident management.

Reference architecture: The blueprint for safe and scalable autonomy in SRE and DevOps

Everyone wants autonomous incident response. Most teams are building it wrong. ‍ The ultimate goal of autonomy in SRE and DevOps is the capacity of a system to not only detect incidents but to resolve them independently through intelligent self-regulation. However, true autonomy isn't born from automating random, isolated tasks. It requires a stable foundation: a Reference Architecture.

Silent Failure in Production ML: Why the Most Dangerous Model Bugs don't Throw Errors

You’ve done it. Your machine learning model is live in production. It’s serving predictions, powering features, and quietly doing its job. Dashboards are green. There are no errors in the logs. Nothing appears broken. And yet, something is wrong. Predictions are getting less reliable. Users are waiting a little longer for responses. Conversion rates are slipping. Trust is eroding, but no alert fires, no system crashes, and no one knows there’s a problem until the damage has been done.

PagerDuty x Backstage Plugin Demo: Eliminate Context Switching for On-Call Engineers

Join Rocío, Product Manager of the Forward Deploying Engineering team at PagerDuty, as she demonstrates how the PagerDuty Backstage plugin transforms incident response by bringing critical operational data directly into your developer portal.

Weekly vs. split-week on-call rotations: A guide to finding the right rhythm

When you move past daily rotations but find anything longer than a week feels too stretched out, you often end up choosing between weekly and split-week rotations. Weekly rotations give you a full seven days before handing off. Split-week rotations break that time into smaller chunks like 2-day, 3-day, or 4-day shifts. Each approach creates a different rhythm for your team. This guide compares both patterns across three key criteria.

PagerDuty + OOPS Meetup: AI in Incident Management

AI is transforming industries at pace, and Incident Response is no exception - raising important questions about how humans and automation should work together when systems are failing and pressure is highest. Panelists:​Andrew White (Technology Director, checkout.com) James Pickles (Senior Solutions Consultant, PagerDuty)​Sarah Wells (Independent Consultant, former Technology Director at FT) Suraj Singh Dadwal (Team Lead, Incident & Problem Management, IG)

Event Intelligence Solutions Part Three: Best Practices for Successful Adoption

As Event Intelligence Solutions (EIS) move from early adoption to operational necessity, many enterprises are realizing that success depends on more than selecting the right technology. For Banking and Financial Services organizations, effective adoption requires a clear strategy, disciplined execution and a strong alignment to business priorities and regulatory demands and not least, customer expectations.