> ## 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. # Opsgenie on Vortex IQ > Monitor Opsgenie performance signals, run automated checks, and prepare approved work through Vortex IQ. Monitor Opsgenie 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) | **20** | **4** | **Build your own** | **Ready to build yours** | **7** | | ------------------- | ---------------- | ------------------ | ------------------------ | -------------- | | performance signals | automated checks | automated fixes | workflows | API operations | ## Monitor performance 20 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 | | --------------------------------------------- | ----------------------- | ---------------------- | ------------------------------------------------------------------------------------------------------------------------- | | **Alerts Firing** | Run operations | Alert band 0 / 50 | Open, un-closed alerts right now - the front-line load on the on-call rotation. | | **Incidents Open** | Run operations | Alert band 0 / 3 | Declared incidents not yet resolved - escalations beyond a single alert. | | **Mean Time To Resolve** | Run operations | Alert band 1800 / 7200 | createdAt -> resolvedAt across incidents. The customer-impact-duration number. | | **Revenue Lost / Min (open incidents)** | Protect revenue | Merchant rule | Live \$/min loss while incidents impacting commerce-critical services are open. The COO's number. | | **SLA Compliance** | Run operations | Alert band 99.9 / 99.5 | % of the period inside SLA across services. The headline reliability commitment number. | | **Services Down** | Run operations | Alert band 0 / 1 | Services with an open incident impacting them - any value above zero is customer-facing. | | **Error Rate** | Customer experience | Alert band 0.5 / 2 | Description pending editorial review; the signal is live. | | **Alert Storm on Commerce-Critical Services** | Protect revenue | Merchant rule | Alert volume on services that front checkout / payments / search, overlaid with order velocity - noise on the money path. | | **Alerts Acknowledged** | Run operations | Merchant rule | Alerts a human has acknowledged - the gap vs Alerts Firing is the un-routed / no-coverage backlog. | | **Incidents Resolved (24h)** | Run operations | Merchant rule | Throughput of the response process over the last day. | | **Mean Time To Acknowledge** | Run operations | Alert band 120 / 600 | createdAt -> acknowledgedAt across alerts. Rising MTTA = on-call routing or coverage gaps. | | **Services Degraded** | Run operations | Alert band 0 / 2 | Services with open alerts but not fully down - early-warning surface. | | **Services Healthy** | Run operations | Merchant rule | Services reporting healthy with no open alerts or incidents. | | **Throughput (req/min)** | Customer experience | Alert band 0 / -10 | Throughput (req/min) over time. | | **Top Alerting Services** | Run operations | Alert band 0 / 100 | Services ranked by alert volume - where the noise (and the on-call burden) concentrates. | | **Top Error Types** | Control risk and change | Alert band 0 / 100 | Alert messages clustered by error type - the recurring failure modes worth fixing at source. | | **Apdex Score** | Customer experience | Alert band 0.95 / 0.7 | Description pending editorial review; the signal is live. | | **Avg Response Time** | Customer experience | Alert band 200 / 1000 | Description pending editorial review; the signal is live. | | **p95 Latency** | Customer experience | Alert band 200 / 1000 | Description pending editorial review; the signal is live. | | **p99 Latency** | Customer experience | Alert band 800 / 3000 | Description pending editorial review; the signal is live. | ## Audit risks and opportunities A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. | Check | Severity | Outcome | Why it matters | Fix status | | ------------------------------------------- | -------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | | **Error rate above 2%** | critical | Customer experience | More than 1 in 50 requests is failing right now. Depending on which endpoints are affected, this can mean pages failing to load, checkout steps failing silently, or background jobs dropping | Report only | | **Apdex score below 0.85** | high | Customer experience | Apdex below 0.85 means a meaningful share of visits are experiencing the site as slow or frustrating rather than satisfying, using the same industry-standard scoring that tells you when perf | Report only | | **Avg response time above 1500ms** | medium | Protect revenue | Average response time over 1.5 seconds is well past the point where shoppers notice the delay, and slow response times are a documented driver of higher bounce and lower conversion; this is | Report only | | **Throughput dropped > 30% week-over-week** | medium | Run operations | Requests handled dropped more than 30% versus the prior week. This can mean genuinely lower traffic (worth knowing on its own) or it can mean the application is silently failing to serve req | Report only | ### Build your own automated fixes 4 checks report findings on Opsgenie 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 **5 read** and **2 write** operations across accounts, alerts, alertacknowledges, alertcloses, alertcounts, incidents on Opsgenie. 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=opsgenie) | Resource | Read operations | Write operations | | ----------------- | --------------- | ---------------- | | accounts | 1 | 0 | | alerts | 1 | 0 | | alertacknowledges | 0 | 1 | | alertcloses | 0 | 1 | | alertcounts | 1 | 0 | | incidents | 1 | 0 | | services | 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 Opsgenie 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.*