SRE Agent: Connectors and Skills

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 and 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.

Navigate to AI Settings SRE Agent Configuration to get started.

Connectors and 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 — automatically or via user request.

Supported Connectors

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

Set up a Connector

1. In the PagerDuty web app, navigate to AI Settings SRE Agent Configuration and click the Connectors tab.
2. Find the connector you want 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 [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.

5. Click Save. The connector appears 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.

Runbook Links

When SRE Agent is provided access to documents, it fetches a document if it determines the document is relevant or if you request it in chat.

Confluence

1. Set up the Workflow Integration and set up the connector.

2. If you have your runbook link configured, the SRE agent should identify it in the event payload.
   1. If the SRE Agent doesn't identify the runbook link, update the event payload in your monitoring tool to include your Confluence runbook link in custom_details using the following nested key:

"custom_details": {
    "runbook_url": {
        "confluence": "https://YOUR-RUNBOOK-LINK"
    }
}

GitHub

1. Set up the Workflow Integration and set up the connector.

2. If you have your runbook link configured, the SRE agent should identify it in the event payload.
   1. If the SRE Agent doesn't identify the runbook link, update the event payload in your monitoring tool to include your GitHub runbook link in custom_details using the following nested key:

"custom_details": {
    "runbook_url": {
        "github": "https://YOUR-RUNBOOK-LINK"
    }
}

ServiceNow

1. Set up the Workflow Integration and set up the connector.
2. If you have your runbook link configured, the SRE agent should identify it in the event payload.
   1. If the SRE Agent doesn't identify the runbook link, update the event payload in your monitoring tool to include your ServiceNow runbook link in custom_details using the following nested key:

"custom_details": {
    "runbook_url": {
        "servicenow": "https://YOUR-RUNBOOK-LINK"
    }
}

Set Custom Details with Orchestration Rules

You can use orchestration rules to update the event payload to include your runbook links in custom_details.

1. Navigate to an orchestration.
2. Navigate to Edit Event Rule Event Fields Add Event Field.
3. Click the Select Field dropdown and add a custom details path to the event field:
   • For GitHub: runbook_url.github
   • For Confluence: runbook_url.confluence
   • For ServiceNow: runbook_url.servicenow

4. Under Replace using, select Template.
5. In Replace with value, paste the URL of the runbook.
6. Click Save.

Best Practices

• Log queries work best when there are query examples in the runbook or alert payload. Sample queries in the alert payload can be in any custom_details field.
• You can also provide queries directly to the agent to help ensure accurate log search.

Prompt Examples

• @pagerduty can you fetch the logs for this incident?
• @pagerduty can you search the logs with this criteria [enter criteria]?

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 retrieved data, 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 is an example of a fully structured skill that you can use as a template. This skill automatically searches Datadog and AWS CloudWatch logs for critical security events during incident triage.

Name: detect-security-incident-logs

Description: 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.

Example Instructions:

When to use:
- 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

Prerequisites:
- Datadog connector configured and active
- AWS CloudWatch connector configured and active

Execution steps:
1. Search Datadog logs for the exact phrase SECURITY_INCIDENT: CRITICAL within the incident time window.
2. Search AWS CloudWatch logs for the exact phrase SECURITY_INCIDENT: CRITICAL within the incident time window.
3. If matches are found in either source, surface the key log details in the SRE Agent response.
4. Recommend triggering the Alert Security Team incident workflow.

Error handling:
- If one connector is unavailable, continue with the other and note which source was skipped.
- If both connectors are unavailable, inform the responder and suggest checking logs manually.

Success criteria:
- The agent has queried both log sources and reported results or confirmed no matches were found.

Examples:
- Alert custom_details contains: type: possible_security_issue
- Responder asks: "Check for any security incidents in the logs"

Create a Skill

Skills can be created through the PagerDuty UI or with the PagerDuty Claude plugin.

In the PagerDuty Web App

1. In the PagerDuty web app, navigate to AI Settings SRE Agent Configure and click the Skills tab.
2. Click Add Skill.
3. On the New Skill page, complete the following fields:

4. Click Save. The skill is immediately available to SRE Agent for all future incidents.

Using the Claude Plugin

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 SRE Agent for all future incidents.

Test a Skill

After creating a skill, trigger an incident that matches your skill's conditions and review what the agent reports in:

• The SRE Agent tab on the incident details page.
• Your ChatOps channel (Slack or Microsoft Teams).