PagerDuty — CyberCLI notification channel

Events API v2 — native ack + escalation policies via your PagerDuty account.

Where to get it

Your PagerDuty account + an Events API v2 integration key.

Install / what you need

No install. Add an Events API v2 integration to a PagerDuty service → copy the routing key.

How to connect

1 Create an Events API v2 integration on your PagerDuty service.
2 Open the dashboard's Notifications panel → Add destination → choose pagerduty, fill in the routing key.
3 CYCON 1/2 triggers an incident; ack/resolve sync back.

When you'd use it

24/7 on-call with escalation policies.

Schedules + overrides for a real SOC rotation.

Ack syncs to the CyberCLI audit chain.

What Herald sends through this channel

2 setup fields · ack-capable

Herald hands every alert to the PagerDutyAdapter as a DispatchPlan. The fields below are what the dashboard form asks for; the sample is the plan the adapter receives. The adapter renders it into the channel-native shape (Discord embeds, Teams MessageCards, PagerDuty Events-API payloads, TwiML, JSON POST bodies) on the way out — that wire transcript varies per channel.

Setup form fields

field	type	required	description / default
integration_key_secret_ref	string	required	PagerDuty Events API v2 routing key (vault ref)
timeout_seconds	number	optional	no description · default: 10

Sample DispatchPlan (input to the adapter)

{
  "decision_id": "tdc-2026-06-20-abc12",
  "channel": "<channel-type>",
  "recipient": {
    "recipient_id": "soc-oncall",
    "display_name": "SOC on-call",
    "addresses": [
      {
        "channel": "<channel-type>",
        "address": "<destination>",
        "min_defcon": 5
      }
    ]
  },
  "urgency": "high",
  "retry_policy": {
    "max_attempts": 3,
    "initial_backoff_seconds": 5
  },
  "subject": "Suspicious login on CEO-LAPTOP",
  "body": "Warden flagged a PowerShell child of WINWORD.EXE. The encoded command resolved to a base64-wrapped Invoke-WebRequest to a newly-registered domain. Trust ladder: L3.",
  "approval_link": "https://app.cybercli.local/approve/abc12",
  "incident_ref": "case-2026-0142",
  "signal_id": "sig-2026-06-20-9f3"
}

Sovereignty: byo_external · Min tier (BYO): business · PagerDuty Events API v2; Business+ only per 3-way poll.

Sovereignty

Incidents route through your PagerDuty account; the routing key is vault-stored.

Who notifies through it

Herald — the Guild's voice role — routes alerts, daily digests, and AI verdicts here, on a per-CYCON-state matrix you control. CYCON 1/2 alerts repeat until an operator acks.

The Guild →

Other Paging channels

Go deeper