CortexDB Docs
Docs for CortexDB 0.12.8, the version running on CortexDB Cloud (api.cortexdb.ai).
Connectors

PagerDuty Connector

Ingest PagerDuty incidents and notes into CortexDB.

Tails PagerDuty incidents and their log entries / notes and writes them to CortexDB as experiences.

Two ways to run this connector

Self-hosted — pip install 'cortexdb-connectors[pagerduty]' then cortexdb-sync sync pagerduty. Managed — CortexDB runs the connector as a worker. See the Connectors overview.

1. Prepare credentials

PagerDuty → Integrations → API Access Keys → create a read-only REST API key and copy it.

What gets written

Each incident (as an issue/observation) and note becomes a POST /v1/experience on the resolved scope (default org:<org>/source:pagerduty), with an entity reference to the incident and metadata (status, urgency, service).

Record keys and threads

  • The internal idempotency_key is the raw PagerDuty incident id or log-entry id (no pd: prefix); pd:incident:<id> is the thread id that links log entries to their incident.
  • Notes link to their incident via a thread=… label, not context.preceded_by.

The key on the wire is derived

The key format above is this connector's internal record identity: it decides which source record an event belongs to. The idempotency_key actually sent to CortexDB is a derived cxsrc:<56 hex> value that also hashes the content, labels, observed time and actor, so an unchanged redelivery converges on the same event while any edit lands as a new one, even where the key format itself is not content-versioned. Every event also carries a source descriptor with the record's fingerprint. See Source identity and keys.

Run it yourself

pip install 'cortexdb-connectors[pagerduty]'
pip install cortexdb-cli && cortexdb init

export PAGERDUTY_API_KEY=...              # required

cortexdb-sync --api-url http://localhost:3141 sync pagerduty
cortexdb-sync --api-url http://localhost:3141 watch pagerduty --interval 120

Optional settings

Set these as environment variables (or the matching keys in the cortexdb-sync YAML config). Lists are comma-separated. For on/off settings, 1, true, yes or on turns the setting on and any other value turns it off.

SettingWhat it doesDefault
PAGERDUTY_SERVICESService IDs to syncEvery service

See also

On this page