Operations | Monitoring | ITSM | DevOps | Cloud

AI is moving out of the experimental phase and into the everyday rhythm of work. Teams are no longer using it occasionally for novelty or quick wins, but instead are exploring more robust use cases to investigate issues, answer questions faster, surface context, and help them move through complex workflows with more confidence. That’s the shift that most organizations’ leadership teams have been asking for.

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.

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.

I have an Upsun project that's nothing but proofs of concept. It's a dashboard, basically. Each POC gets its own tile. Click in, and you land on a page with three tabs. The first tab is a written explanation of what the POC argues. The second tab is the POC itself, with a built-in demo that automates a walkthrough of the feature so the recipient can watch it run without me on the call.

This post covers some techniques to get agents to validate their work. We’ll cover why this is important, a variety of types of checks you can employ, and mechanisms you can use to enforce them.

AI coding tools promise faster development. What they don't show you is the queue forming at the pipeline, the security scanner you bypassed to stay fast, or the cost dashboard with a line now labeled "unknown" that is steadily growing. In May, we shipped 60+ features in 31 days across the entire delivery system: not just the editor, but everything downstream of it.

You don’t have an SRE. There’s no platform team. Your “monitoring strategy” is someone checking Slack for error alerts. When production breaks, the same two or three senior devs drop everything to debug. Sound familiar? Most APM tools are built for organizations with dedicated operations staff. They assume someone has time to configure dashboards, tune alert thresholds, and learn a complex query language. That person does not exist on your team.

You deploy on Friday. Sidekiq starts failing on a job that worked fine in staging. Your error tool shows you a NoMethodError on line 47. But it doesn’t tell you that the job only fails when processing records created after the migration you ran on Thursday. The stack trace is correct and completely useless at the same time. This is the core problem with general-purpose error monitoring on Rails apps. Rails teams deal with N+1 queries that cascade into timeout errors.