PagerDuty
Page your on-call for AI agent incidents in PagerDuty. One PagerDuty incident per correlated AxioRank incident, with trigger, acknowledge, and resolve kept in sync both ways.
The PagerDuty integration turns AxioRank's correlated incidents into PagerDuty incidents and keeps the two in step. A real attack produces many alerts; AxioRank groups them into one incident, and this integration opens exactly one PagerDuty incident for it, with a deep link back and the recommended response actions in the details. Acknowledge or resolve on either side and the other follows.
Available on every plan
Triggering, the incident lifecycle, and two-way sync are all available on Free, Pro, and Team. There is no tier gate.
Add a PagerDuty channel
- In PagerDuty, add an Events API v2 integration to the service you want paged and copy its Integration Key (the routing key).
- In AxioRank, open Channels, click Add Channel, and pick PagerDuty.
- Paste the routing key, choose what pages (see below), set a name, and save.
- Click Send test. It triggers a throwaway incident and immediately resolves it, so you confirm the routing key without leaving an open incident behind.
Routing key encrypted at rest
When a credential key is configured on the deployment, AxioRank encrypts the routing key with AES-256-GCM, bound to your workspace so a ciphertext cannot be reused elsewhere. Channels created before this keep working unchanged.
Page on incidents or on alerts
A PagerDuty channel offers two modes:
- Correlated incidents (recommended). One PagerDuty incident per AxioRank incident, deduplicated on the incident id. AxioRank triggers when the incident opens, acknowledges when it is acknowledged, and resolves when it resolves.
- Every high-risk alert. The original behavior: one trigger per high-risk call. This mode respects the channel's severity floor, quiet hours, and hourly cap.
Severities map to PagerDuty as critical to critical, high to error, medium to warning, and low to info, so your urgency rules and escalation policies apply as written.
Turn on two-way sync
Two-way sync lets a responder's acknowledge or resolve in PagerDuty reflect back onto the AxioRank incident.
- When you create the channel, check Two-way sync. AxioRank shows a webhook URL scoped to that channel.
- In PagerDuty, add a V3 webhook subscription pointing at that URL, and subscribe it to incident.acknowledged and incident.resolved.
- PagerDuty shows a signing secret. Paste it back into AxioRank.
AxioRank verifies every inbound payload against that signing secret before acting, and reflects the acknowledge or resolve onto the matching incident. The reflected update never pages back out, so there is no loop.
The signing secret comes from PagerDuty
PagerDuty mints the signing secret when you create the subscription, so the setup is two steps: AxioRank gives you the URL, then you paste PagerDuty's secret back. A test ping sent before the secret is saved cannot be verified and is rejected, which is expected.
What lands in PagerDuty
Each incident carries:
- a summary with the incident title,
- the severity mapped to PagerDuty,
- custom details with the correlated alert count, blast radius, and the AI triage recommended actions, and
- a link straight to the incident in AxioRank.
Stale incidents that AxioRank auto-resolves are resolved in PagerDuty too, so an untriaged incident that stops recurring does not sit open on your pager.
Slack
Add AxioRank to Slack with one click. Route high-risk AI-agent alerts to a channel, approve or deny held tool calls right in Slack, and run /axiorank for what needs attention.
WordPress
Verify the AI agents that reach your WordPress REST API, admin, and dynamic endpoints with the AxioRank Agent Verification plugin. A thin client of the inbound verify endpoint, with monitor and enforce modes.