# Paige: Connectors and Skills Connect Paige to observability platforms and knowledge bases so it can ground triage recommendations in real system data. Paige, PagerDuty's 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, Paige moves beyond simple alert analysis. - [**Connectors and Tools**](#connectors-and-tools) give Paige 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**](#skills) give Paige 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** → **Paige Configuration** to get started. > **Prerequisites:** Before configuring connectors, ensure the following: > > - You have Admin or Account Owner permissions in PagerDuty. > - You have credentials or API keys for the third-party integrations you plan to connect. ## Connectors and Tools Connectors link Paige 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** → **Paige Configuration** → **Connectors** to view and manage your connectors. | Connector | Tools | Connection Type | | :-------------------- | :-------------- | :--------------- | | **Arize** | Metrics | API | | | Traces | API | | **AWS (CloudWatch)** | Logs | API | | **Azure Monitor** | Logs | API | | **Confluence** | Knowledge Base | API | | **Coralogix** | Logs | API | | **Datadog** | Logs | API | | | Metrics | MCP | | | Traces | MCP | | **Dynatrace** | Logs | API | | **Elasticsearch** | Logs | API | | **GCP** | Logs | API | | **GitHub** | Knowledge Base | API | | | Code | MCP | | | Code (Revert PR) | API | | **Grafana** | Logs | API | | | Metrics | API | | **Honeycomb.io** | Logs | MCP | | | Metrics | MCP | | **Logz.io** | Logs | API | | **New Relic** | Logs | API | | | Metrics | MCP | | | Traces | MCP | | **Observe Inc.** | Logs | MCP | | | Metrics | MCP | | **Sentry** | Logs | API | | **ServiceNow** | Knowledge Base | API | | **Splunk** | Logs | API | | | Metrics | MCP | | **Sumo Logic** | Logs | API | ### Set up a Connector 1. In the PagerDuty web app, navigate to **AI Settings** → **Paige 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 Paige 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 Paige 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](/ai-automation/automation/incident-workflows/workflow-integrations) and [set up the connector](#set-up-a-connector). > **OAuth Access:** If you have set up your OAuth connection to Confluence but the integration is not working, verify that your admin has approved your user access to the PagerDuty app in Confluence. 2. If you have your runbook link configured, Paige should identify it in the event payload. 1. If Paige 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: ```json "custom_details": { "runbook_url": { "confluence": "https://YOUR-RUNBOOK-LINK" } } ``` #### GitHub 1. Set up the [Workflow Integration](/ai-automation/automation/incident-workflows/workflow-integrations) and [set up the connector](#set-up-a-connector). > **Branch Requirement:** Linked documents must already be committed to the main branch and cannot be from a feature branch. 2. If you have your runbook link configured, Paige should identify it in the event payload. 1. If Paige 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: ```json "custom_details": { "runbook_url": { "github": "https://YOUR-RUNBOOK-LINK" } } ``` #### ServiceNow 1. Set up the [Workflow Integration](/ai-automation/automation/incident-workflows/workflow-integrations) and [set up the connector](#set-up-a-connector). 2. If you have your runbook link configured, Paige should identify it in the event payload. 1. If Paige 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: ```json "custom_details": { "runbook_url": { "servicenow": "https://YOUR-RUNBOOK-LINK" } } ``` #### Set Custom Details with Orchestration Rules You can use [orchestration rules](/ai-automation/aiops/event-orchestration#step-2-create-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` ![Configuring a runbook link in event fields](/images/kb/e23e94c9c6502cb5f824251f8c26e398dd536bb965556ab6520bc9404433aa90-screenshot_2026_02_06_at_1_40_01_pm_1.webp) *Configuring a runbook link in event fields* 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 (Available in Early Access):** Arm your agent with specialized domain expertise using custom instructions, scripts, and runbooks. Skills are available through **AI Settings** or the PagerDuty Claude plugin. Skills allow you to arm Paige 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: | Component | Details | | :------------------- | :----------------------------------------------------------------------- | | **When to Use** | Conditions that tell the agent when to invoke this skill automatically. | | **Prerequisites** | The integrations or data the agent needs to execute the skill. | | **Execution Steps** | Step-by-step instructions the agent follows during triage. | | **Error Handling** | How the agent should gracefully degrade if a step fails. | | **Success Criteria** | How the agent determines whether the skill ran successfully. | | **Examples** | Trigger phrases or alert conditions that invoke this skill. | #### 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 Paige's 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** → **Paige** → **Configure** and click the **Skills** tab. 2. Click **Add Skill**. 3. On the **New Skill** page, complete the following fields: | Field | Value | | :------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------- | | **Name** | Enter a unique identifier for the skill (for example, `escalation-runbook`). | | **Description** | Enter a short description of what the skill does (for example, `Guides the agent when escalating incidents`). | | **Instructions** | Enter the full instructions to send to the LLM. Use the structure described in [What a Skill Contains](#what-a-skill-contains) as a guide. | | **Make skill available to everyone** | Check this option to make the skill accessible to all users in the account. When unchecked, the skill is only available to you. | 4. Click **Save**. The skill is immediately available to Paige for all future incidents. ![Creating a skill in the PagerDuty UI](/images/kb/35f9fe4cac2bddbacf68be53fda97be5f5fab322f946c9cf26c8b51fee374326-Screenshot_2026-06-02_at_1.43.14_PM.png) *Create a skill in PagerDuty* #### 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 Paige 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 **Paige** tab on the incident details page. - Your ChatOps channel (Slack or Microsoft Teams).