> ## 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.

# ClickHouse on Vortex IQ

> Monitor ClickHouse health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor ClickHouse 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)

| **32**              | **8**            | **Build your own** | **Ready to build yours** | **7**          |
| ------------------- | ---------------- | ------------------ | ------------------------ | -------------- |
| performance signals | automated checks | automated fixes    | workflows                | API operations |

## Monitor performance

32 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                                                                                                        |
| ---------------------------------------------------------- | ----------------------- | -------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Active Parts (Top 10 Tables)**                           | Protect revenue         | Merchant rule        | From system.parts WHERE active. >1000 parts on a single table = merge backlog risk; can trigger Too Many Parts error. |
| **ClickHouse Event Ingest vs Ecom Orders**                 | Protect revenue         | Merchant rule        | ClickHouse-distinctive XC ,  event ingest typically tracks order/click rate; divergence = pipeline broken.            |
| **ClickHouse Pool Saturation vs Traffic Burst**            | Protect revenue         | Alert band 70 / 90   | ClickHouse 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.                                                                        |
| **Failed Queries (24h)**                                   | Protect revenue         | Alert band 20 / 100  | query\_log WHERE type='ExceptionWhileProcessing'.                                                                     |
| **Inserts per Second (live)**                              | Run operations          | Watch only           | InsertedRows event rate from system.events delta. ClickHouse-distinctive.                                             |
| **Last Successful Backup (hours ago)**                     | Run operations          | Alert band 24 / 72   | Last BACKUP TO S3 / Disk run from system.backups. ClickHouse Cloud: managed snapshots.                                |
| **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).                                                                        |
| **Query Latency p95 (ms)**                                 | Customer experience     | Alert band 50 / 200  | From system.query\_log percentile aggregation.                                                                        |
| **Replication Lag (absolute\_delay)**                      | Run operations          | Alert band 1 / 10    | From system.replicas.absolute\_delay.                                                                                 |
| **Slow Analytics Queries During Checkout Window**          | Protect revenue         | Merchant rule        | Slow Analytics Queries During Checkout Window, broken down by row.                                                    |
| **Slow-Query Rate %**                                      | Customer experience     | Alert band 1 / 5     | query\_log entries with duration\_ms > 1000 as % of total.                                                            |
| **Too Many Parts Error or Parts Count >1000 on Any Table** | Control risk and change | Merchant rule        | ClickHouse-distinctive ,  parts cap hit halts ingest on that table.                                                   |
| **Too Many Parts Errors (24h)**                            | Control risk and change | Merchant rule        | ClickHouse-distinctive ,  Code 252 errors from parts cap hit. Any >0 = ingest broken.                                 |
| **UncompressedCache Hit Rate %**                           | Run operations          | Alert band 95 / 80   | UncompressedCacheHits / (UncompressedCacheHits + UncompressedCacheMisses) from system.events.                         |
| **ClickHouse Health Score**                                | Run operations          | Merchant rule        | Description pending editorial review; the signal is live.                                                             |
| **ClickHouse QPS Spike vs Ecom Order Rate**                | Protect revenue         | 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.                                                             |
| **Queries per Second (live)**                              | Run operations          | Watch only           | 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 p99 (ms)**                                 | Customer experience     | Alert band 100 / 500 | Description pending editorial review; the signal is live.                                                             |
| **MEMORY\_LIMIT\_EXCEEDED (24h)**                          | Control risk and change | Merchant rule        | Query killed by max\_memory\_usage. Spike = a single heavy query swamping the instance.                               |
| **Memory Usage %**                                         | Control risk and change | Merchant rule        | MemoryTracking metric from system.metrics / max\_server\_memory.                                                      |
| **Merges In Progress**                                     | Run operations          | Watch only           | Merge metric from system.metrics. Sustained high = ingest outpacing merge throughput.                                 |
| **Partition Count (Top 10 Tables)**                        | Run operations          | Merchant rule        | From system.parts GROUP BY table COUNT DISTINCT partition\_id.                                                        |
| **Replication Queue Size (Top Tables)**                    | Run operations          | Merchant rule        | From system.replicas.queue\_size. ClickHouse-distinctive ,  pending replication tasks per table.                      |
| **Top 10 Slowest Queries**                                 | Customer experience     | Watch only           | Top 10 Slowest Queries, broken down by row.                                                                           |
| **Active Replicas**                                        | 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.                                                             |
| **Instance Uptime**                                        | Run operations          | Watch only           | 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 |

### Build your own automated fixes

8 checks report findings on ClickHouse 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 systembackups, systembuildoptions, systemevents, systemmetrics, systemparts, systemquerylogs on ClickHouse. 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=clickhouse)

<Accordion title="Browse the operations you can build with">
  | Resource           | Read operations | Write operations |
  | ------------------ | --------------- | ---------------- |
  | systembackups      | 1               | 0                |
  | systembuildoptions | 1               | 0                |
  | systemevents       | 1               | 0                |
  | systemmetrics      | 1               | 0                |
  | systemparts        | 1               | 0                |
  | systemquerylogs    | 1               | 0                |
  | systemreplicas     | 1               | 0                |

  Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
</Accordion>

### Ready to build your first ClickHouse 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.*
