> ## 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. # Databricks on Vortex IQ > Monitor Databricks health, cost and reliability signals, and catch incidents and runaway spend early. Monitor Databricks 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** | **7** | **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 | | ------------------------------------------- | ----------------------- | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Avg Cluster CPU Utilisation %** | Customer experience | Merchant rule | Databricks-distinctive , drives right-sizing decisions for cost + performance. | | **DBU Burn +50% Week-over-Week** | Run operations | Merchant rule | Alerts for DBU Burn +50% Week-over-Week. | | **DBU Burn vs Ecom Order Volume** | Protect revenue | Merchant rule | Databricks-distinctive XC , DBU burn should track ecom volume. Divergence = inefficient pipelines. | | **DBU Burned (24h)** | Run operations | Merchant rule | From billable usage API. Databricks-defining cost metric. Includes job compute + SQL warehouse + interactive. | | **DBU by Cluster (7d)** | Run operations | Watch only | DBU by Cluster (7d). | | **Failed Job Burst (>5 failures in 1h)** | Protect revenue | Merchant rule | Databricks-distinctive , pipeline failures cascade fast across dependent jobs. | | **Failed Jobs (24h)** | Protect revenue | Merchant rule | result\_state=FAILED OR TIMEDOUT. Triage queue. | | **Idle Cluster DBU Wasted (24h)** | Run operations | Merchant rule | DBU spent while cluster had no active jobs. Auto-termination tuning signal. | | **Job Success Rate (24h)** | Protect revenue | Merchant rule | From /jobs/runs/list , Databricks-distinctive defining metric. Failed scheduled runs = data pipelines broken. | | **Last Delta Lake Vacuum / Optimize** | Run operations | Alert band 24 / 72 | Delta Lake doesn't have traditional backup , Time Travel (default 7d retention) + table OPTIMIZE/VACUUM stand in. This tracks last successful OPTIMIZE run on the largest | | **SQL Query Error Rate Spike (>1% in 5m)** | Control risk and change | Alert band 0.1 / 1 | Alerts for SQL Query Error Rate Spike (>1% in 5m). | | **SQL Query Latency p95 (ms)** | Customer experience | Alert band 50 / 200 | Lakehouse SQL p95 measured in seconds typically , threshold reflects warehouse workload. | | **Slow SQL Queries During Checkout Window** | Protect revenue | Merchant rule | Slow SQL Queries During Checkout Window, broken down by row. | | **Active Clusters** | Run operations | Watch only | Description pending editorial review; the signal is live. | | **Databricks Health Score** | Run operations | Merchant rule | Description pending editorial review; the signal is live. | | **Databricks SQL Spike vs Ecom Order Rate** | Protect revenue | Merchant rule | Description pending editorial review; the signal is live. | | **Pipeline Lag (since last success)** | Run operations | Alert band 1 / 10 | Description pending editorial review; the signal is live. | | **Pipeline Lag vs Ecom Order Flow** | Protect revenue | Merchant rule | Description pending editorial review; the signal is live. | | **SQL Queries per Hour (live)** | Run operations | Watch only | Description pending editorial review; the signal is live. | | **SQL Query Error Rate %** | Control risk and change | Alert band 0.1 / 1 | Description pending editorial review; the signal is live. | | **SQL Query Latency p99 (ms)** | Customer experience | Alert band 100 / 500 | Description pending editorial review; the signal is live. | | **SQL Warehouse Saturation %** | Run operations | Alert band 70 / 90 | 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. | | **DLT Pipeline Status Distribution** | Protect revenue | Watch only | Running / Idle / Failed / Stopped , from /pipelines/list. | | **Long-Running Jobs (>1h)** | Run operations | Merchant rule | Jobs still running past expected duration , common cost-runaway pattern. | | **Top 10 Failing Workflows (7d)** | Run operations | Watch only | Top 10 Failing Workflows (7d), broken down by row. | | **Top 10 Slowest SQL Queries** | Customer experience | Watch only | Top 10 Slowest SQL Queries, broken down by row. | | **Active SQL Sessions** | Run operations | Watch only | Description pending editorial review; the signal is live. | | **Active SQL Warehouses** | Run operations | Watch only | Description pending editorial review; the signal is live. | | **Avg DBU per Job Run** | Run operations | Merchant rule | Description pending editorial review; the signal is live. | | **SQL 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 | ### Build your own automated fixes 7 checks report findings on Databricks 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 billableusagedownloads, clusterlists, jobrunlists, pipelines, sqlhistoryquerys, sqlwarehous on Databricks. 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=databricks) | Resource | Read operations | Write operations | | ---------------------- | --------------- | ---------------- | | billableusagedownloads | 1 | 0 | | clusterlists | 1 | 0 | | jobrunlists | 1 | 0 | | pipelines | 1 | 0 | | sqlhistoryquerys | 1 | 0 | | sqlwarehous | 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 Databricks 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.*