PagerDuty

Trigger PagerDuty incidents via the Events API v2. For alerting on pipeline delivery failures, business-rule violations, or anomalous event volumes — not for routing every event to PagerDuty (which would drown an oncall rotation).

⚠️

Status: alpha. Scaffolded entry. Deduplication and incident-grouping keys are configurable per pipeline; defaults will be tuned in a future release.

Prerequisites

A PagerDuty account with a service.
An Events API V2 integration on that service. Configure under Services > your service > Integrations > Events API V2.
The Routing Key (also called “integration key”) from that integration.

Configuration fields

Field	Required	Notes
`routing_key`	Yes	Events API V2 integration/routing key (kept secret).
`severity_default`	No	`critical`, `error`, `warning` (default), or `info`. Applied when severity is not explicitly mapped from the event.

Endpoint

Events are delivered to:

POST https://events.pagerduty.com/v2/enqueue

with a payload shaped per the Events API V2 spec:

{
  "routing_key": "...",
  "event_action": "trigger",
  "payload": {
    "summary": "…",
    "severity": "warning",
    "source": "datafly-signal",
    "custom_details": { ... }
  }
}

Recommended use patterns

Delivery failure threshold: configure a pipeline filter so events are only forwarded when a vendor delivery error rate exceeds a threshold within a rolling window.
Business rule alerts: e.g. trigger a PagerDuty incident when a high-value order (> £10,000) fires, or when a refund event rate spikes.
SLA monitoring: map Signal’s own health metrics to PagerDuty severities for on-call awareness.

Microsoft Teams Pipeline Router