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 PagerDuty Advance Insights Agent (now Generally Available for Microsoft Teams users) builds towards this vision. As AI accelerates development and teams ship more code than ever, operational data is everywhere; insights aren’t.

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 PagerDuty Advance Scribe Agent updates (Generally Available) build towards this vision. When a major operational issue hits, there’s always someone drawing the short straw to take on the most thankless job in incident response: scribing the call. Chances are you were already that someone.

We’ll be rolling out new Slack capabilities to eliminate more manual toil from your incident workflow: click once to promote any alert to an incident, get dedicated channels created automatically, page responders without leaving Slack, and manage all your settings in one place. This is part of our path to autonomous operations: reducing toil, protecting your capacity, and letting you stay in flow. If you’re only using PagerDuty for on-call scheduling, you’re missing the full picture.

AI promise and AI capabilities often diverge, with developers often reporting much faster code production, but not enough change in how incidents are handled. When the rate of change is faster than ever, but the rate of recovery from incidents isn’t moving, developers wind up stuck in firefighting mode. And, when these systems fail, it’s costly. According to PagerDuty’s State of AI-First Operations, over a third of surveyed companies report losing $500K per hour of downtime.