Overview

SRE Agent retrieves log data, metrics, and runbooks from observability platforms and knowledge bases to guide responders through investigation, triage, and resolution. By connecting your observability stack and institutional knowledge, SRE Agent moves beyond simple alert analysis.

• Connectors & Tools give SRE Agent real-time access to your logs and metrics, so every triage analysis is grounded in the actual state of your systems - not just the alert payload.
• Skills give SRE Agent institutional knowledge specific to your environment - your runbooks, your escalation paths, your standards - so it can recommend precise next steps instead of generic ones.

Together, these capabilities help your team triage faster with less human involvement, reducing MTTA and MTTR while building confidence in AI-assisted operations.

Go to AI Settings SRE Agent Configuration to get started.

📘

SaaS Integrations

All of these integrations are SaaS-based.

Availability

📘

Connectors & Tools (Available in Early Access)

Retrieve real-time logs and metrics by connecting SRE Agent to third-party observability platforms via API or MCP.

🚧

Skills (Coming soon to Early Access - May 30, 2026)

Arm your agent with specialized domain expertise using custom instructions, scripts, and runbooks.

Requires the PagerDuty Claude plugin.

Prerequisites

Before configuring connectors, ensure the following:

• Your account is enrolled in the SRE Agent Early Access program.
• You have Admin or Account Owner permissions in PagerDuty.
• You have credentials or API keys for the third-party integrations you plan to connect.
• The SRE Agent is enabled and configured to run via an Incident Workflow.

Connectors & Tools

Connectors link SRE Agent to your external data sources. Once a connector is active, the agent can use its associated Tools - such as querying logs or pulling metrics - will happen automatically or via user request. Currently, Knowledge Base Integrations are invoked automatically when URL is in the event payload, and Observability tools are user invoked unless invoked via an Incident Workflow.

Supported Connectors

Navigate to AI Settings SRE Agent Configuration Connectors to view and manage your connectors.

*(GA - Generally Available, EA - Early Access)

Set up a Connector

1. In the PagerDuty web app, go to AI Settings SRE Agent Configuration and click the Connectors tab.
2. Find the connector to add and click Connect. If the connector is already listed but shows Unhealthy, click the menu to edit or reconnect it.
3. On the **Connect to {{Your integration}} Tools** screen, select an existing connection from the dropdown or click Manage connections to create a new one.
4. Under Agent may use these tools, check the tools you want to enable:
   • Logs (API) - allows SRE Agent to query log data from this source during incident triage.
   • Metrics (MCP) - allows SRE Agent to pull metric data (available on connectors that support it).
5. Click Save. The connector will appear in your list with a status of Active once the connection is established.

Connector Statuses

• Active: The connector is healthy and SRE Agent can use its tools.
• Unhealthy: The connection exists but is failing. Check your credentials or API key and reconnect.
• Not connected: No connection has been set up. Click Connect to configure it.

Skills

Skills allow you to arm SRE Agent with custom instructions, runbooks, and scripts that give it specialized domain expertise. Rather than relying solely on the data it can retrieve, a Skill tells the agent exactly how to handle specific situations, so it can intelligently deduce the next steps for troubleshooting issues even before a human looks at the incident.

What a Skill Contains

Each Skill is a structured set of instructions with the following components:

Example Skill: detect-security-incident-logs

The following example shows a Skill that automatically searches Datadog and AWS CloudWatch logs for critical security events during incident triage.

Skill: detect-security-incident-logs
Searches Datadog and CloudWatch logs for critical security incidents. When SECURITY_INCIDENT: CRITICAL log entries are found, it recommends triggering the 'Alert Security Team' incident workflow.

When to invoke:

• Automatically during initial triage when the alert custom details include type: possible_security_issue
• When a responder asks the agent to check for security incidents

What it does:

• Searches Datadog and CloudWatch logs for the exact phrase SECURITY_INCIDENT: CRITICAL
• If matches are found: surfaces key log details and recommends the Alert Security Team Incident Workflow
• Degrades gracefully if one integration is unavailable - continues with the other

Create a Skill

Skills are configured through the PagerDuty Claude plugin. Each agent type (SRE Agent, Insights Agent, Shift Agent) supports up to five Skills.

1. Install the PagerDuty Claude plugin.
2. Run the /pagerduty:create-pagerduty-skill command and follow the guided prompts to define the Skill's name, instructions, trigger conditions, and metadata.
3. Once created, the Skill is immediately available to the SRE Agent for all future incidents.
4. Test by triggering an incident matching your Skill's conditions and review what the agent reports in the SRE Agent tab on the incident details page or in ChatOps (Slack, Microsoft Teams)