> ## 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. # MySQL on Vortex IQ > Monitor MySQL health, cost and reliability signals, and catch incidents and runaway spend early. Monitor MySQL 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) | **31** | **9** | **Build your own** | **Ready to build yours** | **6** | | ------------------- | ---------------- | ------------------ | ------------------------ | -------------- | | performance signals | automated checks | automated fixes | workflows | API operations | ## Monitor performance 31 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 | | -------------------------------------------------------- | ----------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | **Connection Pool Saturation %** | Run operations | Alert band 70 / 90 | Threads\_connected / max\_connections. | | **Connection Pool at >90% Saturation** | Run operations | Alert band 0 / 1 | Alerts for Connection Pool at >90% Saturation. | | **InnoDB Buffer Pool Hit Rate %** | Run operations | Alert band 95 / 80 | 1 - (Innodb\_buffer\_pool\_reads / Innodb\_buffer\_pool\_read\_requests). MySQL-distinctive , drives every OLTP workload. | | **InnoDB Deadlocks (last 5m)** | Customer experience | Alert band 0 / 5 | Innodb\_deadlocks delta from SHOW ENGINE INNODB STATUS. | | **Last Successful Backup (hours ago)** | Run operations | Alert band 24 / 72 | Last successful mysqldump / Percona XtraBackup / RDS snapshot. | | **MySQL Pool Saturation vs Traffic Burst** | Protect revenue | Alert band 70 / 90 | MySQL Pool Saturation vs Traffic Burst, broken down by row. | | **Queries per Second (live)** | Run operations | Watch only | Questions\_per\_sec from SHOW GLOBAL STATUS, sampled every 5s. | | **Query Error Rate Spike (>1% in 5m)** | Control risk and change | Alert band 0.1 / 1 | Alerts for Query Error Rate Spike (>1% in 5m). | | **Replication Thread Health (IO/SQL)** | Run operations | 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** | Run operations | Alert band 0 / 1 | Alerts for Replication Threads Stopped or Lag Exceeds Threshold. | | **Slow Queries During Checkout Window (5m)** | Protect revenue | Merchant rule | Slow Queries During Checkout Window (5m), broken down by row. | | **Slow-Query Rate %** | Customer experience | Alert band 1 / 5 | Slow\_queries delta / Questions delta from SHOW GLOBAL STATUS. | | **Database Disk Usage %** | Run operations | Alert band 70 / 90 | Description pending editorial review; the signal is live. | | **MySQL Health Score** | Run operations | Merchant rule | Description pending editorial review; the signal is live. | | **MySQL Inventory Rows vs Ecom Inventory Count** | Protect revenue | Merchant rule | Description pending editorial review; the signal is live. | | **MySQL QPS Spike vs Ecom Order Rate** | Protect revenue | Merchant rule | Description pending editorial review; the signal is live. | | **Query Error Rate %** | Control risk and change | Alert band 0.1 / 1 | Description pending editorial review; the signal is live. | | **Query Latency p95 (ms)** | Customer experience | Alert band 50 / 200 | Description pending editorial review; the signal is live. | | **Query Latency p99 (ms)** | Customer experience | Alert band 100 / 500 | Description pending editorial review; the signal is live. | | **Replication Lag (Seconds\_Behind\_Source)** | Run operations | Alert band 1 / 10 | Description pending editorial review; the signal is live. | | **Aborted Connects (24h)** | Control risk and change | Merchant rule | Aborted\_connects from SHOW GLOBAL STATUS. Spike = wrong creds, network issues, or max\_connect\_errors hit. | | **Binlog Backlog (MB) on Primary** | Run operations | Merchant rule | Sum of binlog file sizes ahead of replica position. Growing backlog = replica falling behind. | | **InnoDB Dirty Pages %** | Run operations | Merchant rule | Innodb\_buffer\_pool\_pages\_dirty / Innodb\_buffer\_pool\_pages\_total. High = checkpoint pressure, async write storms. | | **Top 10 Slowest Queries (digest)** | Customer experience | Watch only | Top 10 Slowest Queries (digest), broken down by row. | | **Active Replicas** | Run operations | Watch only | Description pending editorial review; the signal is live. | | **Connection Errors (24h)** | Control risk and change | Merchant rule | Description pending editorial review; the signal is live. | | **Connections In Use** | Run operations | Watch only | Description pending editorial review; the signal is live. | | **InnoDB Free Pages** | Run operations | Merchant rule | Description pending editorial review; the signal is live. | | **Instance Uptime** | Run operations | Watch only | Description pending editorial review; the signal is live. | | **Memory Usage %** | Run operations | Merchant rule | Description pending editorial review; the signal is live. | | **Query Latency p50 (ms)** | Customer experience | Watch only | 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 | | ----------------------------------------------- | -------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | | **Connection pool saturation above 90%** | critical | Customer experience | 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, includin | Report only | | **Disk usage above 90%** | critical | Run operations | 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 | Report only | | **Query error rate above 1% in last 5 minutes** | critical | Run operations | 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 silen | Report only | | **Last successful backup older than 72 hours** | high | Run operations | 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 woul | Report only | | **Replication lag above 10 seconds** | high | Run operations | 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 r | Report only | | **Slow-query rate above 5% of total** | high | Customer experience | 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 datab | Report only | | **p95 query latency above 200ms sustained 15m** | high | Customer experience | 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 | Report only | | **Buffer / cache hit rate below 80%** | medium | Run operations | 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 o | Report only | | **Deadlocks detected (>0 in last 5 minutes)** | medium | Protect revenue | A 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 a | Report only | ### Build your own automated fixes 9 checks report findings on MySQL 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 **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 **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=mysql) | 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 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected. ### Ready 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. *** *Generated from the connector capability graph. Counts reflect the servable registry after alias normalisation and de-duplication, and refresh automatically when the registry changes.*