Capabilities
What you get with the PagerDuty integration
Incident creation
Critical SLA breaches and severe anomalies trigger PagerDuty incidents. Each incident includes the violated contract, affected event, severity, and a direct link to the violation in suky.
Severity mapping
Map suky alert severities to PagerDuty urgencies. Critical SLA breaches become high-urgency incidents; warnings become low-urgency notifications.
Escalation-aware routing
Incidents are routed to the right PagerDuty service and escalation policy. Data engineering, analytics, and product teams each get their own rules.
Deduplicated incidents
Repeated breaches of the same rule and event collapse into one PagerDuty incident via a stable dedup key, so on-call isn't paged twice for the same problem.
Setup
How to connect PagerDuty
Go to Settings → Alerts → PagerDuty in suky.
Paste your PagerDuty integration or routing key.
Configure severity mapping (which suky alert levels trigger incidents).
Send a test alert to verify the connection and routing.
Ready to connect PagerDuty?
Invite-only while we onboard the Founding 25 — request an invite and I'll set you up.