> ## 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. # Sentry on Vortex IQ > Monitor Sentry health, cost and reliability signals, and catch incidents and runaway spend early. Monitor Sentry 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) | **19** | **4** | **Build your own** | **Ready to build yours** | **10** | | ------------------- | ---------------- | ------------------ | ------------------------ | -------------- | | performance signals | automated checks | automated fixes | workflows | API operations | ## Monitor performance 19 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 | | ---------------------------- | ----------------------- | ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Incidents Open** | Grow revenue | Alert band 0 / 1 | Open metric-alert incidents right now. Any open incident on a checkout-adjacent project is revenue-relevant. | | **Mean Time To Resolve** | Run operations | Alert band 1800000 / 3600000 | Average incident-open duration. Creeping MTTR is the canary for accumulating tech debt or thin on-call cover. | | **Revenue at Risk (live)** | Protect revenue | Merchant rule | Sentry incident/error state × commerce-sibling baseline = \$/min at risk while the error rate is elevated. The single most-valuable card in this manifest. | | **Services Down** | Run operations | Alert band 0 / 1 | Projects with crash-free rate below the critical floor or no events flowing. Any non-zero value is a page. | | **Alerts Acknowledged** | Run operations | Watch only | Alerts a human has acknowledged - separates 'someone is on it' from 'firing into the void'. | | **Alerts Firing** | Run operations | Alert band 0 / 1 | Metric-alert rules currently in the firing state - the live count of things breaching their threshold. | | **Apdex Score** | Customer experience | Alert band 0.95 / 0.7 | Sentry performance Apdex over the satisfaction threshold. Below 0.85 = users feeling the slowness. | | **Avg Response Time** | Customer experience | Alert band 200 / 1000 | Mean transaction duration across the org/project. Baseline for latency-regression detection. | | **Error Rate** | Customer experience | Alert band 0.5 / 2 | Share of transactions/requests returning errors, from Sentry events. Rising = a release or dependency regressed. | | **Incidents Resolved (24h)** | Run operations | Watch only | Incidents closed in the last 24h - throughput of the on-call response, not just the backlog size. | | **Mean Time To Acknowledge** | Run operations | Merchant rule | Average gap from incident trigger to first human acknowledgement. The page-fatigue early-warning. | | **SLA Compliance** | Run operations | Alert band 99.9 / 99.5 | Crash-free / availability attainment against the SLA target. Below 99.5% means the budget is being eaten. | | **Services Degraded** | Run operations | Alert band 0 / 3 | Projects breaching a warning threshold but not down - the early-warning column before an outage. | | **Services Healthy** | Control risk and change | Watch only | Count of projects whose error rate + crash-free rate are inside healthy bounds. The green column. | | **Throughput (req/min)** | Customer experience | Alert band 0 / -10 | Transactions per minute. A sustained drop can mean an outage upstream or a broken instrumentation path. | | **Top Alerting Services** | Run operations | Watch only | Projects ranked by incident/alert volume - where on-call attention and reliability investment should go first. | | **Top Error Types** | Run operations | Watch only | Error classes ranked by occurrence count - the fix-this-first list, ordered by blast radius. | | **p95 Latency** | Customer experience | Alert band 200 / 1000 | 95th-percentile transaction duration - the slow tail most customers never see but the worst ones do. | | **p99 Latency** | Protect revenue | Alert band 200 / 1000 | 99th-percentile transaction duration - the worst-case experience and the timeout-risk signal. | ## 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 Sentry 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 **1 write** operations across organizationissues, organizations, organizationalertrules, organizationevents, organizationeventstats, organizationincidents on Sentry. 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=sentry) | Resource | Read operations | Write operations | | ---------------------- | --------------- | ---------------- | | organizationissues | 1 | 1 | | organizations | 1 | 0 | | organizationalertrules | 1 | 0 | | organizationevents | 1 | 0 | | organizationeventstats | 1 | 0 | | organizationincidents | 1 | 0 | | organizationprojects | 1 | 0 | | organizationsessions | 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 Sentry 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.*