> ## 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. # Atlassian Statuspage on Vortex IQ > Monitor Atlassian Statuspage performance signals, run automated checks, and prepare approved work through Vortex IQ. Monitor Atlassian Statuspage 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** | **14** | | ------------------- | ---------------- | ------------------ | ------------------------ | -------------- | | 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 Component Health × Sales** | Protect revenue | Merchant rule | Checkout-component status overlaid with order volume - when the component degrades, sales follow. | | **Revenue at Risk (live)** | Protect revenue | Merchant rule | Live \$/min loss while any component is in major\_outage and a commerce sibling reports velocity. The COO's number. | | **Alerts Acknowledged** | Run operations | Merchant rule | Incidents moved to identified - cause is known and a fix is in flight. | | **Alerts Firing** | Run operations | Alert band 0 / 3 | Published incidents still in the investigating state - the page is openly telling customers something is wrong. | | **Apdex Score** | Customer experience | Alert band 0.95 / 0.7 | Satisfied/tolerating/frustrated ratio derived from the system metrics published to the status page. 0.94+ is healthy. | | **Incidents Open** | Run operations | Alert band 0 / 3 | Unresolved incidents published on the status page 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 creation to the identified/monitoring update - how fast the team confirms a cause. | | **Mean Time To Resolve** | Run operations | Alert band 1800000 / 3600000 | Average gap from incident creation to resolution - how fast published incidents actually get closed. | | **SLA Compliance** | Run operations | Alert band 99.9 / 99.5 | Rolling component-group availability vs the SLA target. 99.9% is two-nines-plus; below 99.5% is a breach. | | **Services Degraded** | Customer experience | Alert band 0 / 2 | Components in degraded\_performance or partial\_outage - the early-warning band before a full outage. | | **Services Down** | Run operations | Alert band 0 / 1 | Components in major\_outage - customer-facing outage surface published to the status page. | | **Services Healthy** | Run operations | Alert band 0 / -10 | Components reporting operational across the status page. | | **Throughput (req/min)** | Customer experience | Alert band 0 / -10 | Throughput (req/min) over time. | | **Top Alerting Services** | Run operations | Merchant rule | Components / groups generating the most incidents - where to spend reliability effort first. | | **Top Error Types** | Control risk and change | Merchant rule | Most common incident impact bands / failure causes across published incidents. | | **Avg Response Time** | Customer experience | Alert band 200 / 1000 | Description pending editorial review; the signal is live. | | **Error Rate** | Customer experience | Alert band 0.5 / 2 | 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 | | ------------------------------------------- | -------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | | **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 Atlassian Statuspage 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 **11 read** and **3 write** operations across pageincidents, pagecomponents, pages, pagecomponentgroups, pageincidentunresolveds, pagemetrics on Atlassian Statuspage. 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=statuspage) | Resource | Read operations | Write operations | | ----------------------- | --------------- | ---------------- | | pageincidents | 2 | 2 | | pagecomponents | 2 | 1 | | pages | 2 | 0 | | pagecomponentgroups | 1 | 0 | | pageincidentunresolveds | 1 | 0 | | pagemetrics | 1 | 0 | | pagemetricsdatas | 1 | 0 | | pagesubscribers | 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 Atlassian Statuspage 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.*