> ## 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. # CockroachDB on Vortex IQ > Monitor CockroachDB health, cost and reliability signals, and catch incidents and runaway spend early. Monitor CockroachDB 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) | **30** | **8** | **Build your own** | **Ready to build yours** | **7** | | ------------------- | ---------------- | ------------------ | ------------------------ | -------------- | | performance signals | automated checks | automated fixes | workflows | API operations | ## Monitor performance 30 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 | | ----------------------------------------------- | ----------------------- | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Block Cache Hit Rate %** | Control risk and change | Alert band 95 / 80 | rocksdb\_block\_cache\_hits / (hits + misses) from the Admin HTTP API /\_status/vars - cumulative since node start. Requires admin\_http\_url; the SQL-only connection alone can | | **CRDB Pool Saturation vs Traffic Burst** | Protect revenue | Alert band 70 / 90 | CRDB Pool Saturation vs Traffic Burst, broken down by row. | | **Connection Pool at >90% Saturation** | Run operations | Alert band 70 / 90 | Alerts for Connection Pool at >90% Saturation. | | **Last Successful Backup (hours ago)** | Run operations | Alert band 24 / 72 | Last BACKUP TO S3 / GCS run. For Cloud: managed backups dashboard. | | **Range Lease Balance Skew %** | Run operations | Merchant rule | (max leaseholder\_count - min leaseholder\_count) / total leases. >25% = hot node. CockroachDB-distinctive. | | **Slow Statements During Checkout Window (5m)** | Protect revenue | Merchant rule | Slow Statements During Checkout Window (5m), broken down by row. | | **Statement Error Rate Spike (>1% in 5m)** | Control risk and change | Alert band 0.1 / 1 | Alerts for Statement Error Rate Spike (>1% in 5m). | | **Top Contended Statements** | Customer experience | Merchant rule | CockroachDB-distinctive , distributed transactions surface contention via crdb\_internal.cluster\_contention\_events. | | **Unavailable Ranges** | Run operations | Merchant rule | CockroachDB-distinctive , ranges lacking quorum. Any >0 = some data unavailable for reads/writes. | | **Unavailable or Under-Replicated Ranges** | Protect revenue | Merchant rule | CockroachDB-distinctive , quorum loss or replication gap. Any unavailable = data loss risk. | | **Under-Replicated Ranges** | Control risk and change | Merchant rule | Ranges below configured replication factor , typically self-heals; sustained >0 = balancer overloaded or node down. | | **CRDB Inventory Rows vs Ecom Inventory** | Protect revenue | Merchant rule | Description pending editorial review; the signal is live. | | **CRDB Statements Spike vs Ecom Order Rate** | Protect revenue | Merchant rule | Description pending editorial review; the signal is live. | | **Cluster Node Count** | Run operations | Merchant rule | Description pending editorial review; the signal is live. | | **CockroachDB Health Score** | Run operations | Merchant rule | Description pending editorial review; the signal is live. | | **Connection Pool Saturation %** | Run operations | Alert band 70 / 90 | Description pending editorial review; the signal is live. | | **Database Disk Usage %** | Run operations | Alert band 70 / 90 | Description pending editorial review; the signal is live. | | **Raft Quiescent Lag (seconds)** | Run operations | Alert band 1 / 10 | Description pending editorial review; the signal is live. | | **Slow-Query Rate %** | Customer experience | Alert band 1 / 5 | Description pending editorial review; the signal is live. | | **Statement Error Rate %** | Control risk and change | Alert band 0.1 / 1 | Description pending editorial review; the signal is live. | | **Statement Latency p95 (ms)** | Customer experience | Alert band 50 / 200 | Description pending editorial review; the signal is live. | | **Statement Latency p99 (ms)** | Customer experience | Alert band 100 / 500 | Description pending editorial review; the signal is live. | | **Statements per Second (live)** | Run operations | Watch only | Description pending editorial review; the signal is live. | | **Decommissioning Nodes** | Run operations | Merchant rule | Nodes in decommission state , long-running = stuck draining ranges. | | **Replicas per Node** | Run operations | Watch only | Replicas per Node, compared across items. | | **Transaction Retries (24h)** | Catalogue quality | Merchant rule | CockroachDB-distinctive , distributed transactions retry on conflict. High retries = contention hotspot. | | **Active Nodes (status=live)** | Run operations | Watch only | Description pending editorial review; the signal is live. | | **Connections In Use** | 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. | | **Statement 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 | ### Build your own automated fixes 8 checks report findings on CockroachDB 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 **7 read** and **0 write** operations across crdbinternalclustercontentionevents, crdbinternalclustersettings, crdbinternalgossipnodes, crdbinternalnodestatementstatistics, crdbinternalranges, show nodes on CockroachDB. 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=cockroachdb) | Resource | Read operations | Write operations | | ----------------------------------- | --------------- | ---------------- | | crdbinternalclustercontentionevents | 1 | 0 | | crdbinternalclustersettings | 1 | 0 | | crdbinternalgossipnodes | 1 | 0 | | crdbinternalnodestatementstatistics | 1 | 0 | | crdbinternalranges | 1 | 0 | | show nodes | 1 | 0 | | statusvars | 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 CockroachDB 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.*