31
performance signals
9
automated checks
0
prepared fixes
0
proven workflows
6
API operations
- Overview
- Monitor (31)
- Audit (9)
- 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
31 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 (17 signals)
Run operations (17 signals)
| Signal | Alert behaviour | What it tracks |
|---|---|---|
| Active Replicas | Watch only | Description pending editorial review; the signal is live. |
| Binlog Backlog (MB) on Primary | Merchant rule | Sum of binlog file sizes ahead of replica position. Growing backlog = replica falling behind. |
| Connection Pool Saturation % | Alert band 70 / 90 | Threads_connected / max_connections. |
| Connection Pool at >90% Saturation | Alert band 0 / 1 | Alerts for Connection Pool at >90% Saturation. |
| Connections In Use | Watch only | Description pending editorial review; the signal is live. |
| Database Disk Usage % | Alert band 70 / 90 | Description pending editorial review; the signal is live. |
| InnoDB Buffer Pool Hit Rate % | Alert band 95 / 80 | 1 - (Innodb_buffer_pool_reads / Innodb_buffer_pool_read_requests). MySQL-distinctive , drives every OLTP workload. |
| InnoDB Dirty Pages % | Merchant rule | Innodb_buffer_pool_pages_dirty / Innodb_buffer_pool_pages_total. High = checkpoint pressure, async write storms. |
| InnoDB Free Pages | Merchant rule | Description pending editorial review; the signal is live. |
| Instance Uptime | Watch only | Description pending editorial review; the signal is live. |
| Last Successful Backup (hours ago) | Alert band 24 / 72 | Last successful mysqldump / Percona XtraBackup / RDS snapshot. |
| Memory Usage % | Merchant rule | Description pending editorial review; the signal is live. |
| MySQL Health Score | Merchant rule | Description pending editorial review; the signal is live. |
| Queries per Second (live) | Watch only | Questions_per_sec from SHOW GLOBAL STATUS, sampled every 5s. |
| Replication Lag (Seconds_Behind_Source) | Alert band 1 / 10 | Description pending editorial review; the signal is live. |
| Replication Thread Health (IO/SQL) | Merchant rule | Replica_IO_Running + Replica_SQL_Running must both be Yes. MySQL-distinctive , either thread stopped = replication broken. |
| Replication Threads Stopped or Lag Exceeds Threshold | Alert band 0 / 1 | Alerts for Replication Threads Stopped or Lag Exceeds Threshold. |
Customer experience (6 signals)
Customer experience (6 signals)
| Signal | Alert behaviour | What it tracks |
|---|---|---|
| InnoDB Deadlocks (last 5m) | Alert band 0 / 5 | Innodb_deadlocks delta from SHOW ENGINE INNODB STATUS. |
| Query Latency p50 (ms) | Watch only | Description pending editorial review; the signal is live. |
| Query Latency p95 (ms) | Alert band 50 / 200 | Description pending editorial review; the signal is live. |
| Query Latency p99 (ms) | Alert band 100 / 500 | Description pending editorial review; the signal is live. |
| Slow-Query Rate % | Alert band 1 / 5 | Slow_queries delta / Questions delta from SHOW GLOBAL STATUS. |
| Top 10 Slowest Queries (digest) | Watch only | Top 10 Slowest Queries (digest), broken down by row. |
Protect revenue (4 signals)
Protect revenue (4 signals)
| Signal | Alert behaviour | What it tracks |
|---|---|---|
| MySQL Inventory Rows vs Ecom Inventory Count | Merchant rule | Description pending editorial review; the signal is live. |
| MySQL Pool Saturation vs Traffic Burst | Alert band 70 / 90 | MySQL Pool Saturation vs Traffic Burst, broken down by row. |
| MySQL QPS Spike vs Ecom Order Rate | Merchant rule | Description pending editorial review; the signal is live. |
| Slow Queries During Checkout Window (5m) | Merchant rule | Slow Queries During Checkout Window (5m), broken down by row. |
Control risk and change (4 signals)
Control risk and change (4 signals)
| Signal | Alert behaviour | What it tracks |
|---|---|---|
| Aborted Connects (24h) | Merchant rule | Aborted_connects from SHOW GLOBAL STATUS. Spike = wrong creds, network issues, or max_connect_errors hit. |
| Connection Errors (24h) | Merchant rule | Description pending editorial review; the signal is live. |
| Query Error Rate % | Alert band 0.1 / 1 | Description pending editorial review; the signal is live. |
| Query Error Rate Spike (>1% in 5m) | Alert band 0.1 / 1 | Alerts for Query Error Rate Spike (>1% in 5m). |
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-002p95 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-001Deadlocks detected (>0 in last 5 minutes)
Deadlocks detected (>0 in last 5 minutes)
Severity medium · Outcome Protect revenue · Fix status Report onlyA deadlock means two operations blocked each other and the database had to kill one of them; whatever that transaction was doing (placing an order, updating stock, writing a record) failed and, depending on how the application handles it, may not have been retried.Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.Reference:
DB-PERF-003Build 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 6 read and 0 write operations across performanceschemaeventstatementsummarybydigests, performanceschemaprocesslists, show engine innodb status, show global status, show replica status, show variables on MySQL. 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 MySQL 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 |
|---|---|---|
| performanceschemaeventstatementsummarybydigests | 1 | 0 |
| performanceschemaprocesslists | 1 | 0 |
| show engine innodb status | 1 | 0 |
| show global status | 1 | 0 |
| show replica status | 1 | 0 |
| show variables | 1 | 0 |