Trigger SRE Agent via Escalation Policy

Add the SRE Agent to an escalation level to put it on call as a virtual responder, in parallel with your human responders — not in place of them. The moment an incident triggers, the SRE Agent begins investigating alongside whoever is paged next in your escalation chain. It reviews the incident payload, checks how similar incidents were resolved in the past, and queries your connected integrations for relevant logs and runbooks.

By the time a human responder opens the incident, the SRE Agent has already gathered context, investigated likely causes, and — where available — recommended a workflow with its reasoning attached. The human is never blocked waiting on the agent, and the agent never blocks waiting on a human; both start working the moment the incident fires.

Prerequisites

• The SRE Agent is enabled for your PagerDuty account.
• You have a Manager or Admin role, which is required to edit escalation policies.

Add the SRE Agent to an Escalation Policy

1. Navigate to the escalation policy you want to configure and open it.

2. Select the escalation level where you want the SRE Agent to engage. The SRE Agent triggers immediately after the incident is created, in parallel with that level's on-call responder.

3. Turn on Trigger SRE Agent for incidents in this escalation policy.

   

4. Choose where the SRE Agent posts its findings. You can enable one or both destinations:

   • Post in the SRE Agent side panel in PagerDuty — investigation results appear in the SRE Agent panel on the incident.
   • Post investigation results in Slack — results post to the incident's dedicated Slack channel if one exists, or to the relevant team or service channel where the incident notification was posted.

5. Click Save. Once saved, every incident that reaches this escalation level triggers the SRE Agent automatically, with no manual assignment needed per incident.