> ## 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. # Apache Cassandra on Vortex IQ > Monitor Apache Cassandra health, cost and reliability signals, and catch incidents and runaway spend early. Monitor Apache Cassandra 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) | **29** | **8** | **Build your own** | **Ready to build yours** | **10** | | ------------------- | ---------------- | ------------------ | ------------------------ | -------------- | | performance signals | automated checks | automated fixes | workflows | API operations | ## Monitor performance 29 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 | | ------------------------------------------------- | ----------------------- | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Cassandra Health Score** | Run operations | Merchant rule | Composite of node-up ratio, latency percentiles, pending compactions and dropped mutations. | | **Cassandra NTR Saturation vs Ecom Burst** | Protect revenue | Alert band 70 / 90 | Cassandra NTR Saturation vs Ecom Burst, broken down by row. | | **Cassandra Product Table Count vs Ecom Catalog** | Protect revenue | Merchant rule | Cassandra-distinctive XC - many merchants store catalog / inventory in Cassandra; drift = product-sync broken. | | **Coordinator Read Latency p95 (ms)** | Customer experience | Alert band 50 / 200 | ClientRequest Read latency p95 from system\_views.coordinator\_read\_latency / Read MBean. Storefront-facing. | | **Disk Usage %** | Run operations | Alert band 70 / 90 | Load / data-directory usage from nodetool status Load column vs disk capacity. | | **Dropped Mutations (24h)** | Protect revenue | Merchant rule | DroppedMessages (MUTATION). Coordinator shed a write under load - silent data loss risk if hints also dropped. | | **Dropped Mutations or Hinted-Handoff Growth** | Grow revenue | Merchant rule | Alerts for Dropped Mutations or Hinted-Handoff Growth. | | **Hinted Handoffs Pending** | Run operations | Merchant rule | Cassandra-distinctive - hints stored for unreachable replicas. Growing = a replica is down or slow; data not yet converged. | | **JVM Heap Used %** | Run operations | Merchant rule | Cassandra runs on the JVM - heap >75% drives GC pauses; sustained high heap precedes node instability. | | **Key Cache Hit Rate %** | Run operations | Alert band 95 / 80 | KeyCache hit\_ratio from the system\_views.caches CQL virtual table (4.0+) / org.apache.cassandra.metrics:type=Cache,scope=KeyCache,name=HitRate MBean. Low hit rate = more | | **Last Snapshot Age (hours)** | Grow revenue | Alert band 24 / 72 | Most recent nodetool snapshot (or Medusa / Astra backup). Gated: requires snapshot tooling visibility. | | **Native-Transport Pool Saturation %** | Run operations | Alert band 70 / 90 | Native-Transport-Requests active / max threads from system\_views.thread\_pools. | | **Node Down (DN) or Gossip Flapping** | Run operations | Merchant rule | Cassandra-distinctive - a DN node reduces replica availability; sustained = consistency-level failures imminent. Page on-call. | | **Nodes Up / Normal (UN)** | Run operations | Merchant rule | Count of endpoints in UN state from nodetool status / system.peers. Cassandra-defining - DN node = reduced replica availability. | | **Operations per Second (read + write, live)** | Run operations | Watch only | ClientRequest Read + Write count delta from system\_views / org.apache.cassandra.metrics MBeans. | | **Pending Compactions** | Run operations | Merchant rule | Cassandra-distinctive - from nodetool compactionstats / PendingTasks MBean. Backlog = SSTables stacking up, read amplification rising. | | **Request Error Rate %** | Control risk and change | Alert band 0.1 / 1 | ClientRequest Failures + Timeouts + Unavailables as % of total reads + writes. | | **Request Error Rate Spike (>1% in 5m)** | Control risk and change | Alert band 0.1 / 1 | Alerts for Request Error Rate Spike (>1% in 5m). | | **Slow Reads During Checkout Window (5m)** | Protect revenue | Merchant rule | Slow Reads During Checkout Window (5m), broken down by row. | | **Slow-Query Rate %** | Customer experience | Alert band 1 / 5 | Share of ClientRequest Read+Write samples over 200ms, from the EstimatedHistogram buckets behind org.apache.cassandra.metrics:type=ClientRequest,scope={Read,Write},name=L | | **Tombstones Scanned per Read** | Customer experience | Merchant rule | Cassandra-distinctive - TombstoneScannedHistogram. High tombstone reads cause latency + can trip the 100k failure threshold. | | **Cassandra Write Spike vs Ecom Order Rate** | Protect revenue | Merchant rule | Description pending editorial review; the signal is live. | | **Coordinator Read Latency p99 (ms)** | Customer experience | Alert band 100 / 500 | Description pending editorial review; the signal is live. | | **Coordinator Write Latency p99 (ms)** | Customer experience | Alert band 100 / 500 | ClientRequest Write latency p99. Writes are normally cheap in Cassandra - high p99 = commitlog / GC pressure. | | **Last Repair Age (hours)** | Protect revenue | Merchant rule | Repair recency vs gc\_grace\_seconds (default 10d). Stale repair = zombie data / resurrected deletes risk. | | **Native-Transport Connections** | Run operations | Watch only | Connected client count from system\_views.clients. | | **Read Timeouts (24h)** | Control risk and change | Merchant rule | ClientRequest Read Timeouts - coordinator didn't get enough replica responses inside read\_request\_timeout. | | **SSTables per Read (avg)** | Run operations | Merchant rule | SSTablesPerReadHistogram - high count = compaction falling behind, every read touches more files. | | **Coordinator Read 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 Apache Cassandra 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 **10 read** and **0 write** operations across nodetool compactionstats, nodetool netstats, nodetool status, nodetool tablestats, nodetool tpstats, select \* from systemlocals on Apache Cassandra. 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=cassandra) | Resource | Read operations | Write operations | | -------------------------------- | --------------- | ---------------- | | nodetool compactionstats | 1 | 0 | | nodetool netstats | 1 | 0 | | nodetool status | 1 | 0 | | nodetool tablestats | 1 | 0 | | nodetool tpstats | 1 | 0 | | select \* from systemlocals | 1 | 0 | | select \* from systempeers | 1 | 0 | | select \* from systemviewclients | 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 Apache Cassandra 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.*