> ## 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. # Better Uptime on Vortex IQ > Monitor Better Uptime health, cost and reliability signals, and catch incidents and runaway spend early. Monitor Better Uptime health, cost and reliability signals, and catch incidents and runaway spend early. 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** | **2** | **Build your own** | **Ready to build yours** | **12** | | ------------------- | ---------------- | ------------------ | ------------------------ | -------------- | | 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 | | ----------------------------------- | ----------------------- | ---------------------------- | ----------------------------------------------------------------------------------------------------- | | **Checkout Monitor Health × Sales** | Protect revenue | Merchant rule | Checkout-monitor up/down overlaid with order volume - when the check fails, sales follow. | | **Revenue at Risk (live)** | Protect revenue | Merchant rule | Live \$/min loss while any monitor is DOWN and a commerce sibling reports velocity. The COO's number. | | **Alerts Acknowledged** | Run operations | Merchant rule | Incidents acknowledged by an on-call responder - work is in flight. | | **Alerts Firing** | Run operations | Alert band 0 / 3 | Incidents currently in the Started state - alerts that have fired but not yet been picked up. | | **Apdex Score** | Customer experience | Watch only | Satisfied/tolerating/frustrated ratio derived from monitor response times. 0.94+ is healthy. | | **Incidents Open** | Run operations | Alert band 0 / 3 | Unresolved incidents across all monitors right now. | | **Incidents Resolved (24h)** | Run operations | Merchant rule | Incidents closed in the last 24 hours - recovery throughput. | | **Mean Time To Acknowledge** | Run operations | Alert band 300000 / 900000 | Average gap from incident start to first acknowledgement - responsiveness of the on-call rota. | | **Mean Time To Resolve** | Run operations | Alert band 1800000 / 3600000 | Average gap from incident start to resolution - how fast things actually get fixed. | | **SLA Compliance** | Run operations | Alert band 99.9 / 99.5 | Rolling availability vs the SLA target. 99.9% is two-nines-plus; below 99.5% is a breach. | | **Services Degraded** | Run operations | Watch only | Monitors responding slowly or partially - the early-warning band before down. | | **Services Down** | Run operations | Alert band 0 / 1 | Monitors currently failing their check - customer-facing outage surface. | | **Services Healthy** | Run operations | Alert band 0 / -10 | Monitors reporting up across the fleet. | | **Throughput (req/min)** | Customer experience | Alert band 0 / -10 | Throughput (req/min) over time. | | **Top Alerting Services** | Run operations | Merchant rule | Monitors generating the most incidents - where to spend reliability effort first. | | **Top Error Types** | Control risk and change | Merchant rule | Most common failure causes / status codes across failing checks. | | **Avg Response Time** | Customer experience | Alert band 200 / 1000 | Description pending editorial review; the signal is live. | | **Error Rate** | Customer experience | Watch only | Description pending editorial review; the signal is live. | | **p95 Latency** | Customer experience | Alert band 800 / 1500 | Description pending editorial review; the signal is live. | | **p99 Latency** | Customer experience | Alert band 1500 / 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 | | ------------------------------------------- | -------- | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | | **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 2 checks report findings on Better Uptime 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 **9 read** and **3 write** operations across monitors, incidents, escalationpolicys, incidentacknowledges, incidentresolves, monitorgroups on Better Uptime. 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=better-uptime) | Resource | Read operations | Write operations | | -------------------- | --------------- | ---------------- | | monitors | 2 | 1 | | incidents | 2 | 0 | | escalationpolicys | 1 | 0 | | incidentacknowledges | 0 | 1 | | incidentresolves | 0 | 1 | | monitorgroups | 1 | 0 | | monitorresponsetimes | 1 | 0 | | monitorslas | 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 Better Uptime 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.*