29
performance signals
12
automated checks
0
prepared fixes
0
proven workflows
6
API operations
- Overview
- Monitor (29)
- Audit (12)
- Automate
What you can achieve
Capabilities are grouped around merchant outcomes, not API terminology.Run operations
Monitor orders, fulfilment, delivery and settlement.
Customer experience
Find storefront, speed, accessibility and journey problems.
Protect revenue
Find failures, leaks and risks before they cost sales.
Control risk and change
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.1
Connect
Authorise the source. Scopes are shown before access is granted.
2
Monitor
Watch the signals against your own baselines, not universal defaults.
3
Detect
Run checks and gather evidence specific to your store.
4
Recommend
Explain what happened, why it matters and the proposed action.
5
Approve
You review scope, risk and reversibility before anything changes.
6
Execute
Apply through governed connector operations.
7
Verify
Confirm the intended result and keep the receipt.
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.Run operations (15 signals)
Run operations (15 signals)
| 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). |
Customer experience (6 signals)
Customer experience (6 signals)
| 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. |
Protect revenue (5 signals)
Protect revenue (5 signals)
| 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. |
Control risk and change (3 signals)
Control risk and change (3 signals)
| 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.Connection pool saturation above 90%
Connection pool saturation above 90%
Severity critical · Outcome Customer experience · Fix status Report onlyAt 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-001Disk usage above 90%
Disk usage above 90%
Severity critical · Outcome Run operations · Fix status Report onlyA 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-002Query error rate above 1% in last 5 minutes
Query error rate above 1% in last 5 minutes
Severity critical · Outcome Run operations · Fix status Report onlyMore 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-001Last successful backup older than 72 hours
Last successful backup older than 72 hours
Severity high · Outcome Run operations · Fix status Report onlyIf 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-001Replication lag above 10 seconds
Replication lag above 10 seconds
Severity high · Outcome Run operations · Fix status Report onlyAnything 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-001Slow-query rate above 5% of total
Slow-query rate above 5% of total
Severity high · Outcome Customer experience · Fix status Report onlyMore 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-002WLM Queue Length >5 Sustained 5m
WLM Queue Length >5 Sustained 5m
Severity high · Outcome Run operations · Fix status Report onlyQueues 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-003p95 query latency above 200ms sustained 15m
p95 query latency above 200ms sustained 15m
Severity high · Outcome Customer experience · Fix status Report onlyOne 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 customerVortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.Reference:
DB-PERF-001Buffer / cache hit rate below 80%
Buffer / cache hit rate below 80%
Severity medium · Outcome Run operations · Fix status Report onlyMore 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-001Queries Spilling to Disk >10 in 24h
Queries Spilling to Disk >10 in 24h
Severity medium · Outcome Customer experience · Fix status Report onlyQueries 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-004Tables With >10% Unsorted Rows (VACUUM Candidate)
Tables With >10% Unsorted Rows (VACUUM Candidate)
Severity medium · Outcome Customer experience · Fix status Report onlyTables 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-001Tables With Stale Statistics (ANALYZE Candidate)
Tables With Stale Statistics (ANALYZE Candidate)
Severity low · Outcome Customer experience · Fix status Report onlyStale 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-002Build 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 workflowReady 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.Browse the operations you can build with
Browse the operations you can build with
| 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 |