What it unlocks
Trigger incidents
Agents can create PagerDuty incidents for insights that cross the severity bar you set.
Acknowledge and resolve
State flows both ways. Acking in PagerDuty reflects in RubixKube, and vice versa, so the same incident is not worked twice.
RCA attached
Every incident triggered by RubixKube carries a link to the RCA report (or the insight, if an RCA has not landed yet).
Tenant-wide by default
Enable once. Every agent across every environment can use PagerDuty.
Connect it
Authenticate
Authorise with PagerDuty. An admin completes the flow and picks the services RubixKube can reach.
How the agents use it
- When an insight crosses the severity bar, agents can trigger the right PagerDuty service and attach the RCA (or the insight, if the RCA is still in flight).
- Ack and resolve state stays in sync, so the on-call person does not see a ghost incident in RubixKube after they have worked it in PagerDuty.
Build custom workflows with skills
The connection exposes trigger and update capabilities. Specific workflows (per-team service routing, tighter thresholds for regulated environments, quieter thresholds for lab, auto-follow-up if the page has not been acked within N minutes) are built as Skills. Skills are where you shape paging behaviour to your on-call model.Troubleshooting
Pages do not fire
Pages do not fire
Confirm the service is still connected in Integrations → PagerDuty and the severity threshold is set to a level the insight actually crosses.
Ack does not sync back to RubixKube
Ack does not sync back to RubixKube
Reauthorise the integration to refresh webhooks. Webhook delivery from PagerDuty can also be delayed briefly under load.
Related guides
Slack
Pair PagerDuty with Slack for day-to-day comms.
Skills
How to compose paging capabilities into custom workflows.