PagerDuty Connector

The PagerDuty connector ingests incidents, alerts, and on-call changes into CortexDB as event episodes. This enables your AI systems to reason about incident history, patterns, and on-call context.

Setup

CORTEX_PAGERDUTY_API_KEY=your-pagerduty-api-key
CORTEX_PAGERDUTY_SERVICES=P1ABC2D,P3EFG4H
CORTEX_PAGERDUTY_TENANT_ID=my-app

cortexdb-connector pagerduty \
  --api-key your-pagerduty-api-key \
  --services "P1ABC2D,P3EFG4H" \
  --tenant-id my-app

What Gets Ingested

| PagerDuty Event | Episode Type | Content | |---|---|---| | Incident triggered | event | Incident title and details | | Incident resolved | event | Resolution summary | | Alert fired | event | Alert details | | On-call change | event | Schedule change | | Postmortem | document | Postmortem content |

Episode Example

{
  "type": "event",
  "content": "Incident triggered: Payments API latency > 5s. Service: payments-api. Urgency: high. Assigned to: alice.",
  "source": "pagerduty",
  "timestamp": "2026-03-15T03:00:00Z",
  "metadata": {
    "incident_id": "P12345",
    "service": "payments-api",
    "urgency": "high",
    "status": "triggered",
    "assigned_to": "alice",
    "escalation_policy": "engineering-primary"
  }
}

Configuration

| Variable | Default | Description | |---|---|---| | CORTEX_PAGERDUTY_API_KEY | Required | PagerDuty REST API key | | CORTEX_PAGERDUTY_SERVICES | All | Comma-separated service IDs | | CORTEX_PAGERDUTY_TENANT_ID | Required | Target tenant | | CORTEX_PAGERDUTY_NAMESPACE | pagerduty | Target namespace | | CORTEX_PAGERDUTY_INCLUDE_RESOLVED | true | Include resolved incidents | | CORTEX_PAGERDUTY_BACKFILL_DAYS | 90 | Days of history to backfill | | CORTEX_PAGERDUTY_POLL_INTERVAL_SEC | 30 | Polling interval |