Operations | Monitoring | ITSM | DevOps | Cloud

This blog post is part of PagerDuty’s ongoing series on how we’re helping customers navigate their journey towards autonomous operations. Read on to learn about how PD Automation Runner, now in Early Access, builds towards this vision. Your on-call engineer gets paged for a critical alert on a self-hosted Kubernetes cluster. If this were a cloud-hosted service, Workflow Actions and the SRE Agent would already be working the problem: pulling logs, checking health, surfacing a fix.

This blog post is part of PagerDuty’s ongoing series on how we’re helping customers navigate their journey towards autonomous operations. Read on to learn about how Scoped OAuth for Public Apps, now in Early Access, builds towards this vision. Your security team asks a simple question during a routine review: which third-party apps can reach our PagerDuty data right now, and what exactly can they do with it?

With AI agents and AI-generated code becoming the norm in modern enterprise software, backend systems are evolving faster than ever. And it’s leaving most operations teams with an impossible choice: burn out senior talent on repetitive firefighting, or hand production over to untrained AI agents. With disruptions costing enterprises an average of $300,000 per hour, manual firefighting isn’t an option.

In a 2025 analysis spanning over 100 large language models, Veracode found that nearly half (45%) of AI-generated code causes known security issues and vulnerabilities. Novel risks are being introduced into your operations systems faster than humans can manage or review. At the same time, studies suggest that human review isn’t all that effective, especially beyond 400 lines of code. But AI-generated code isn’t inherently bad. It just doesn’t always work across your whole system.

As the world is racing to plug AI into nearly every part of business, especially software engineering, the stakes to maintain operational integrity have never been higher. AI-generated code and AI-agents ship faster than human SREs can prepare for, which can create costly issues down the line: incidents get harder to predict and more expensive to recover from.

This blog post is part of PagerDuty’s ongoing series on how we’re helping customers navigate their journey towards autonomous operations. Read on to learn about how Event Enrichment builds towards this vision. Every on-call engineer knows the drill. An alert fires. It tells you something is wrong, but not what it means. Is this asset in maintenance? Which team owns it? Is it customer-facing?

This blog post is part of PagerDuty’s ongoing series on how we’re helping customers navigate their journey towards autonomous operations. Read on to learn about how recent SRE Agent Enhancements build towards this vision. During an incident, everything is competing for attention at once. Responders lose time swiveling between tools, insights gathered by AI stay siloed instead of feeding into the next decision, and the pressure to move fast means learnings rarely stick.

This blog post is part of PagerDuty’s ongoing series on how we’re helping customers navigate their journey towards autonomous operations. Read on to learn about how Custom Field Mapping for PagerDuty’s plugin for both Spotify for Backstage and Spotify Portal for Backstage now generally available builds towards this vision. It’s 2am. A Sev-1 fires, and your on-call responder opens the incident in PagerDuty. What’s waiting for them? A service name, and not much else. No tier.

In December 2025, an AI coding agent at AWS suddenly decided to delete and rebuild an entire production environment, causing a 13-hour service disruption and a PR headache for Amazon. As rapid adoption of AI leads to more high-profile, revenue-impacting incidents, resilience has moved from a technical concern to a board-level financial risk.

It’s 2:47 p.m. Your checkout service has been down for 11 minutes. Customers are screenshotting errors and calling in. Your CEO walks into your office and starts asking questions. In this moment, there are two kinds of IT leaders: Whether you walk out with more budget authority (and executive trust) or less depends on your answers, and the infrastructure that supports them. But preparation isn’t just about surviving the incident. It’s actually a revenue opportunity.