> ## 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. # Amazon Redshift on Vortex IQ > Monitor Amazon Redshift health, cost and reliability signals, and catch incidents and runaway spend early. Monitor Amazon Redshift health, cost and reliability signals, and catch incidents and runaway spend early. [Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=redshift) performance signals automated checks automated fixes workflows API operations ### What you can achieve Capabilities are grouped around merchant outcomes, not API terminology. Monitor orders, fulfilment, delivery and settlement. Find storefront, speed, accessibility and journey problems. Find failures, leaks and risks before they cost sales. Keep tracking, access and change under governed control. ### From connection to verified outcome The controlled sequence every capability follows. Nothing changes a connected system without the approval step. Authorise the source. Scopes are shown before access is granted. Watch the signals against your own baselines, not universal defaults. Run checks and gather evidence specific to your store. Explain what happened, why it matters and the proposed action. You review scope, risk and reversibility before anything changes. Apply through governed connector operations. Confirm the intended result and keep the receipt. 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. ### Monitor performance 29 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system. | Signal | Alert behaviour | What it tracks | | -------------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------- | | **Active Connections** | Watch only | CloudWatch DatabaseConnections. | | **Avg WLM Queue Wait (ms)** | Merchant rule | Avg WLM wait before execution from STV\_WLM\_QUERY\_STATE / query queue\_time. | | **CPU Utilisation %** | Merchant rule | CloudWatch CPUUtilization (leader + compute average). | | **Connection Saturation %** | Alert band 70 / 90 | DatabaseConnections / max\_connections. Redshift caps at 500 (default) - saturation = app login timeouts. | | **Cross-Region Snapshot Lag (s)** | Alert band 1 / 10 | Lag of cross-region automated snapshot copy (disaster-recovery replica freshness). | | **Disk Space Used %** | Alert band 70 / 90 | CloudWatch PercentageDiskSpaceUsed. Full disks fail writes, vacuums and sorts - the #1 Redshift outage cause. | | **Disk Space Used >90%** | Alert band 0 / 1 | Alerts for Disk Space Used >90%. | | **Largest Table (GB)** | Watch only | From SVV\_TABLE\_INFO.size - top tables drive disk pressure. | | **Last Snapshot Age (hours)** | Alert band 24 / 72 | Age of the most recent automated/manual snapshot (DescribeClusterSnapshots). Redshift auto-snapshots on a schedule. | | **Max Table Distribution Skew** | Merchant rule | Redshift-distinctive - SVV\_TABLE\_INFO.skew\_rows. High skew = one slice does all the work (bad DISTKEY). | | **Queries Completed / sec** | Watch only | CloudWatch QueriesCompletedPerSecond - live throughput. | | **Tables Needing VACUUM** | Merchant rule | Redshift-distinctive - SVV\_TABLE\_INFO.unsorted. High unsorted rows = full scans = slow queries + wasted disk. | | **Tables with Stale Statistics** | Merchant rule | SVV\_TABLE\_INFO.stats\_off - stale ANALYZE leads the planner to bad join orders. | | **WLM Queue Length** | Merchant rule | Redshift-distinctive - CloudWatch WLMQueueLength. Sustained queueing = under-provisioned WLM / add concurrency scaling. | | **WLM Queueing Sustained (>5 queued)** | Alert band 0 / 1 | Alerts for WLM Queueing Sustained (>5 queued). | | Signal | Alert behaviour | What it tracks | | ---------------------------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Queries Spilling to Disk (24h)** | Merchant rule | Redshift-distinctive - queries spilling to disk (SVL\_QUERY\_SUMMARY is\_diskbased) indicate undersized memory / bad joins. | | **Query Latency p50 (ms)** | Watch only | From SYS\_QUERY\_HISTORY.elapsed\_time percentiles. | | **Query Latency p95 (ms)** | Alert band 50 / 200 | Warehouse p95 measured over analytics queries - threshold reflects warehouse, not OLTP, use. | | **Result Cache Hit Rate %** | Alert band 95 / 80 | Share of queries in the last hour served from the Redshift result cache (SYS\_QUERY\_HISTORY.result\_cache\_hit) - same query set already read for Slow-Qu | | **Slow-Query Rate %** | Alert band 1 / 5 | Share of queries with elapsed\_time over the 5s slow threshold (SYS\_QUERY\_HISTORY). | | **Top 10 Slowest Queries** | Watch only | Top 10 Slowest Queries, broken down by row. | | Signal | Alert behaviour | What it tracks | | ------------------------------------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------------ | | **Query Error Rate %** | Alert band 0.1 / 1 | Aborted / errored queries over total (SYS\_QUERY\_HISTORY.status = 'failed'). | | **Redshift Connection Saturation vs Traffic Burst** | Alert band 70 / 90 | Redshift Connection Saturation vs Traffic Burst, broken down by row. | | **Redshift Query Spike vs Ecom Order Rate** | Merchant rule | Query load should track business volume. Divergence = runaway job / dashboard storm burning warehouse spend. | | **Redshift Table Row Count vs Ecom Catalog Size** | Merchant rule | Redshift-distinctive XC - ecom data lands in Redshift via ETL; row drift = pipeline / sync failure. | | **Slow Analytics Queries During Checkout Window (5m)** | Merchant rule | Slow Analytics Queries During Checkout Window (5m), broken down by row. | | Signal | Alert behaviour | What it tracks | | -------------------------------------- | ------------------ | ---------------------------------------------------------------------------------- | | **Queries Blocked on Locks** | Merchant rule | From STV\_LOCKS / SVV\_TRANSACTIONS - blocked transactions waiting on locks. | | **Query Error Rate Spike (>1% in 5m)** | Alert band 0.1 / 1 | Alerts for Query Error Rate Spike (>1% in 5m). | | **Redshift Health Score** | Merchant rule | Composite of disk usage, WLM queueing, query error rate and connection saturation. | ### 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. Open a check for the detail. **Severity** critical · **Outcome** Customer experience · **Fix status** Report only At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `DB-CAP-001` **Severity** critical · **Outcome** Run operations · **Fix status** Report only A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `DB-CAP-002` **Severity** critical · **Outcome** Run operations · **Fix status** Report only More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `DB-ERR-001` **Severity** high · **Outcome** Run operations · **Fix status** Report only If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `DB-BAK-001` **Severity** high · **Outcome** Run operations · **Fix status** Report only Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `DB-REP-001` **Severity** high · **Outcome** Customer experience · **Fix status** Report only More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `DB-PERF-002` **Severity** high · **Outcome** Run operations · **Fix status** Report only Queues sustained above 5 in workload management mean the cluster is undersized or a workload is misplaced; everything behind it runs late. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `RS-CAP-003` **Severity** high · **Outcome** Customer experience · **Fix status** Report only One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `DB-PERF-001` **Severity** medium · **Outcome** Run operations · **Fix status** Report only More than 1 in 5 reads is missing the cache and going to disk instead, which is markedly slower. This shows up as everything the database does feeling incrementally heavier, rather than as one obvious failure. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `DB-CACHE-001` **Severity** medium · **Outcome** Customer experience · **Fix status** Report only Queries spilling to disk run orders of magnitude slower than in memory; the offending queries are identifiable and usually tunable. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `RS-PERF-004` **Severity** medium · **Outcome** Customer experience · **Fix status** Report only Tables over 10 percent unsorted degrade every scan that touches them; VACUUM restores the performance already paid for. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `RS-MAINT-001` **Severity** low · **Outcome** Customer experience · **Fix status** Report only Stale statistics mislead the query planner into bad plans; ANALYZE is the cheapest performance fix the cluster has. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `RS-MAINT-002` #### Build your own automated fixes Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change. ### Automate approved work Vortex IQ is integrated with **0 read** and **6 write** operations across cloudwatch:getmetricdatas, redshift:describeclusters, redshift:describeclustersnapshots, redshiftdata:describestatements, redshiftdata:executestatements, redshiftdata:getstatementresults on Amazon Redshift. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words. Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=redshift) #### Ready to build your first Amazon Redshift 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. | Resource | Read operations | Write operations | | --------------------------------- | --------------- | ---------------- | | cloudwatch:getmetricdatas | 0 | 1 | | redshift:describeclusters | 0 | 1 | | redshift:describeclustersnapshots | 0 | 1 | | redshiftdata:describestatements | 0 | 1 | | redshiftdata:executestatements | 0 | 1 | | redshiftdata:getstatementresults | 0 | 1 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.