PagerDuty introduced Paige on November 3 as an AI agent intended to help operations teams investigate incidents.

The big change

  • Paige brings incident context and proposed responses into the responder’s workflow.
  • Teams set what it can access and may approve suggested actions.
  • Deep Investigation and SRE Workbench are experiments in PD Labs preview.

PagerDuty says Paige combines alerts and telemetry with past incident context to suggest fixes. A team can review a proposed runbook action before approval. The company describes autonomous handling of defined incidents as coming soon, rather than an available general capability.

In the experimental SRE Workbench, responders can ask Paige to investigate, add context and steer its work. The guide describes a shared timeline, findings and supporting evidence, plus action review and approval. As an incident develops, the team can add information and consider whether the explanation still fits.

The Paige documentation says console access requires both PagerDuty AI and AIOps; Slack or incident-page access requires PagerDuty AI. Requests in Slack or the Operations Console use four AI Actions. Plan and usage terms therefore matter, while Labs features may change.

A separate Incident-Arena preprint evaluated agents on 20 fault-injected tasks using deployed open-source applications in temporary Kubernetes clusters. Researchers reported diagnosis mistakes, incomplete repairs and unsafe regressions. The benchmark checks whether repairs work and avoid unsafe regressions. It did not evaluate Paige.

In a different integration, AWS describes limiting its DevOps Agent’s ServiceNow tool access. Earlier BIG CHANGE coverage discussed the related ServiceNow developments. The AWS integration uses tool-level access controls.