cd /news/ai-agents/sre-agent-enhancements-faster-triage… · home topics ai-agents article
[ARTICLE · art-87538] src=pagerduty.com ↗ pub= topic=ai-agents verified=true sentiment=↑ positive

SRE Agent Enhancements: Faster Triage, Greater Access Controls, Deeper System Connectivity by Ariel Russo

PagerDuty announced enhancements to its SRE Agent, including early access for escalation policy triggering, general availability for incident workflow triggering, connectors, tools, team-level permissions, and recommended incident workflows, enabling faster triage and deeper system connectivity. The agent can now be triggered before a human acknowledges the page, and new governance features allow admins to scope AI to specific teams. These updates aim to accelerate autonomous operations and improve incident response.

read3 min views2 publishedAug 5, 2026
SRE Agent Enhancements: Faster Triage, Greater Access Controls, Deeper System Connectivity by Ariel Russo
Image: Pagerduty (auto-discovered)

Ariel RussoAugust 5, 2026 | 4 min read 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. The same issues creep back in a few weeks later, and the cycle starts over.

Earlier this year, PagerDuty introduced SRE Agent as a virtual responder, one that gathers signals from across your stack to help teams triage, diagnose, and remediate, using memory from past incidents and continuous learning to improve future responses. Since then, we’ve been rolling out enhancements that make the agent faster to configure, easier to trust, and more capable the moment an incident fires. Here’s what’s new.

Triage Before a Human Even Looks

SRE Agent can now be intelligently triggered through Escalation Policies (EA) or incident workflows (GA). Configure it to jump into action the moment an incident triggers, or set criteria based on priority or severity, and the agent joins the incident pre-armed with triage data and memory of past incidents.

That means investigation and analysis can be well underway before a responder ever acknowledges the page. When you finally do open the incident, you’re not starting from zero.

A Faster Way to Extend the Agent

We also introduced a new configuration experience for agent connectors, tools, and skills.

Connectors (GA) plug the agent into third-party data sources like Grafana, New Relic, and Datadog through MCP or API, just enter credentials and authorize. **Tools **(GA) let the agent retrieve logs, metrics, and traces from observability platforms like Datadog, or pull context from knowledge bases like Confluence and GitHub. Skills (EA) arm the agent with custom instructions and domain expertise tailored to your environment, and teams can create them directly from Claude or PagerDuty for use in Slack or the PagerDuty web platform.

Together, these let SRE Agent deduce troubleshooting steps before a human even opens the incident.

Governance Built for Enterprise Rollout

Customers told us they wanted more control over which teams could use agents, and how that access scales across the org. PagerDuty Advance team-level permissions (GA) let you scope AI to specific teams, giving admins the governance layer needed to roll out agentic AI with confidence rather than guesswork.

Recommendations, With the Reasoning Behind Them

Beyond investigation and diagnosis, SRE Agent can now recommend the right course of action through **Recommended Incident Workflows **(GA). It analyzes your existing configured workflows and suggests the one that best fits the current incident, along with the reasoning behind the call.

That reasoning matters as much as the recommendation itself. Responders don’t just get told what to do, they see why the agent landed there, so they can validate the call and build trust in the system over time.

Seeing It Come Together

Here’s what that looks like end to end: an incident triggers, and SRE Agent, already assigned through the escalation policy, begins autonomous triage immediately. By the time a responder opens the incident, the agent has already gathered context, investigated likely causes, and identified a recommended workflow, complete with reasoning drawn from how similar incidents were resolved in the past. The responder reviews the recommendation, runs the workflow, and the agent confirms the fix worked and resolves the incident. It even generates a new runbook, so remediation is faster the next time a similar issue comes up.

That’s the flywheel behind Autonomous Operations: today’s incident becomes tomorrow’s prevention, powered by data at scale, intelligent automation, and a system that keeps getting smarter.

Try It Yourself

These capabilities are rolling out now, with several available as part of Early Access. Watch the full demo to see in action the SRE Agent enhancements for faster triage, greater access controls, and deeper system connectivity.

Want early access SRE Agent on Escalation Policies? Sign up at pagerduty.com/early-access.

── more in #ai-agents 4 stories · sorted by recency
── more on @pagerduty 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/sre-agent-enhancemen…] indexed:0 read:3min 2026-08-05 ·