> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # PagerDuty on Vortex IQ > Monitor PagerDuty performance signals, run automated checks, and prepare approved work through Vortex IQ. Monitor PagerDuty performance signals, run automated checks, and prepare approved work through Vortex IQ. No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls. [Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) | **21** | **0** | **Build your own** | **Ready to build yours** | **9** | | ------------------- | ---------------- | ------------------ | ------------------------ | -------------- | | performance signals | automated checks | automated fixes | workflows | API operations | ## Monitor performance 21 performance signals. Signals with an alert band can raise Nerve Centre alerts; every signal supports a merchant-configured watcher. | Signal | Outcome | Alert behaviour | What it tracks | | ----------------------------------------- | ----------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------- | | **Active Incidents** | Run operations | Alert band 0 / 1 | Open triggered/acknowledged incidents right now. Sev1/sev2 = someone should be paged and moving. | | **Event Submission Success Rate** | Control risk and change | Alert band 99.9 / 99 | Events accepted by the Events API v2 / total submitted. Below 99% = pages are being dropped. | | **Mean Time to Acknowledge** | Run operations | Alert band 300 / 900 | Median alert-generation → acknowledgement. The headline on-call responsiveness number. | | **Revenue at Risk (open sev1 incidents)** | Protect revenue | Merchant rule | Live $/min loss while a sev1 incident sits open. Turns 'an incident is on' into 'this is costing $X/min'. | | **Revoked / Rotated Routing Keys** | Control risk and change | Merchant rule | Services whose Events API v2 key is revoked or rotated - Vortex IQ pages here silently fail. Highest-leverage fix. | | **Routing Key Health** | Run operations | Alert band 100 / 95 | % of services with an active, mapped routing key. Any revoked/rotated/unmapped key = a page that goes nowhere. | | **Un-Acked Pages During Peak Sales** | Protect revenue | Merchant rule | A sev1 page nobody acknowledged while orders were flowing - the worst-case missed-page during revenue hours. | | **Escalation Rate** | Customer experience | Alert band 10 / 30 | % of incidents that escalated past the first responder. Rising = first-line is overloaded or under-staffed. | | **Fail-Open Audit-Logged Events** | Control risk and change | Merchant rule | Events the API could not accept that fell back to the audit log - investigate each, none should be silently lost. | | **Inactive Webhook Subscriptions** | Run operations | Alert band 0 / 1 | Subscriptions toggled off - state changes stop flowing back with no error, the quietest failure mode. | | **Incident Volume by Service** | Customer experience | Merchant rule | Which services page most - the noisiest surfaces to tune or invest in. | | **MTTA by Severity** | Customer experience | Merchant rule | Acknowledgement speed split sev1/sev2/sev3 - sev1 must be fastest. | | **Mean Time to Resolve** | Customer experience | Alert band 3600 / 14400 | Trigger → resolved, the incident lifecycle length. Trending up means incidents are getting stickier. | | **Median Submission Latency** | Run operations | Alert band 1000 / 5000 | Time from alert generation to PagerDuty acceptance. Latency here delays the page. | | **On-Call Schedule Gaps (next 24h)** | Run operations | Alert band 0 / 1 | Uncovered windows in the on-call schedule - a page during the gap escalates to nobody. | | **Retried Submissions (429/5xx)** | Run operations | Merchant rule | Events that needed exponential-backoff retry. A spike means PagerDuty-side throttling or an outage. | | **Sev1 Policies Without Always-On Rota** | Run operations | Merchant rule | Sev1-mapped escalation policies that lack a 24/7 rota or any escalation step - looks wired, isn't. | | **Severity Tiers Without a Service** | Run operations | Merchant rule | A Vortex IQ severity tier (sev1/sev2/sev3) with no PagerDuty service mapped - those alerts have nowhere to route. | | **Submission Success by Service** | Run operations | Merchant rule | Per-service acceptance rate - isolates which routing key / service is dropping events. | | **Webhook Back-Sync Lag** | Run operations | Alert band 30 / 300 | Time between a PagerDuty state change (ack/escalate/resolve) and Vortex IQ ingest. Lag = a stale incident timeline. | | **Webhook Delivery Failures (24h)** | Protect revenue | Merchant rule | Webhook subscriptions with a failed last delivery - back-sync is broken until they recover. | ## Audit risks and opportunities No automated checks are defined for PagerDuty yet; performance signals above cover the monitoring layer, and checks arrive with the connector's audit module. ### Build your own automated fixes 0 checks report findings on PagerDuty today. Turn any finding into an automated fix with a Vortex IQ workflow: **13,885 read and write operations across 229 connectors** are available as building blocks, with approval, verification and rollback on every change. ## Automate approved work Vortex IQ is integrated with **7 read** and **2 write** operations across incidents, abilitys, analyticsmetricsincidentalls, enqueues, escalationpolicys, schedules on PagerDuty. Combine them with anything from the **13,885 operations across 229 connectors** to automate the work in your own words. Changes follow the merchant's configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. Read-only operations do not modify the connected system. [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=pagerduty) | Resource | Read operations | Write operations | | ---------------------------- | --------------- | ---------------- | | incidents | 2 | 0 | | abilitys | 1 | 0 | | analyticsmetricsincidentalls | 0 | 1 | | enqueues | 0 | 1 | | escalationpolicys | 1 | 0 | | schedules | 1 | 0 | | services | 1 | 0 | | webhooksubscriptions | 1 | 0 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected. ### Ready to build your first PagerDuty workflow Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build. *** *Generated from the connector capability graph. Counts reflect the servable registry after alias normalisation and de-duplication, and refresh automatically when the registry changes.*