> ## 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. # Snowflake on Vortex IQ > Monitor Snowflake health, cost and reliability signals, and catch incidents and runaway spend early. Monitor Snowflake 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** | **15** | **Build your own** | **Ready to build yours** | **8** | | ------------------- | ---------------- | ------------------ | ------------------------ | -------------- | | 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 | | ---------------------------------------------------- | ----------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Avg Cost per Query (\$)** | Run operations | Merchant rule | (credits \* \$/credit) / query\_count. Rising = inefficient queries OR more results returned per query. | | **Avg Query Queue Depth per Warehouse** | Customer experience | Merchant rule | From QUEUED\_PROVISIONING\_TIME + QUEUED\_OVERLOAD\_TIME in QUERY\_HISTORY. Snowflake-distinctive , sustained queue = warehouse undersized. | | **Credit Burn +50% Week-over-Week** | Run operations | Merchant rule | Snowflake-distinctive , runaway query / scheduled job overrun is the #1 cost surprise. | | **Credit Burn vs Ecom Order Volume** | Protect revenue | Merchant rule | Snowflake-distinctive XC , credit burn should track ecom volume (more data to analyse = more credits). Divergence = cost inefficiency. | | **Credits Burned (24h)** | Run operations | Merchant rule | From METERING\_HISTORY. Snowflake-defining , credits = dollars burned in compute time. | | **Credits by Warehouse (7d)** | Run operations | Watch only | Per-warehouse credit consumption. Drives sizing + scheduling decisions. | | **Last Snapshot Age (hours)** | Run operations | Alert band 24 / 72 | Snowflake auto-snapshots via Time Travel (default 1d, up to 90d on Enterprise). This reflects Time Travel retention floor. | | **Query Error Rate Spike (>1% in 1h)** | Control risk and change | Alert band 0.1 / 1 | Alerts for Query Error Rate Spike (>1% in 1h). | | **Query Latency p95 (ms)** | Customer experience | Alert band 50 / 200 | Snowflake p95 measured in seconds, not ms , threshold reflects analytics use case. | | **Slow Analytics Queries During Checkout Window** | Protect revenue | Merchant rule | Slow Analytics Queries During Checkout Window, broken down by row. | | **Storage Used (TB)** | Grow revenue | Alert band 70 / 90 | From STORAGE\_USAGE table (1.5hr latency). Storage is cost-anchored , growth = bill growth. | | **Warehouse Cache Hit Rate %** | Customer experience | Alert band 95 / 80 | Avg of ACCOUNT\_USAGE.QUERY\_HISTORY.PERCENTAGE\_SCANNED\_FROM\_CACHE (0-1, scaled to %) over the trailing hour - Snowflake-distinctive: local warehouse SSD cache vs remote mi | | **Warehouse Queueing Sustained (>5 queries queued)** | Run operations | Alert band 70 / 90 | Alerts for Warehouse Queueing Sustained (>5 queries queued). | | **Warehouse Saturation %** | Run operations | Alert band 70 / 90 | running\_queries / max\_concurrency\_level per warehouse , sustained 100% indicates need to upsize or multi-cluster. | | **Cross-Account Replication Lag (s)** | Run operations | Alert band 1 / 10 | Description pending editorial review; the signal is live. | | **Queries per Hour (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. | | **Slow-Query Rate %** | Customer experience | Alert band 1 / 5 | Description pending editorial review; the signal is live. | | **Snowflake Event Ingest vs Ecom Orders** | Protect revenue | Merchant rule | Description pending editorial review; the signal is live. | | **Snowflake Health Score** | Run operations | Merchant rule | Description pending editorial review; the signal is live. | | **Snowflake QPS Spike vs Ecom Order Rate** | Protect revenue | Merchant rule | Description pending editorial review; the signal is live. | | **Failed Logins (24h)** | Protect revenue | Merchant rule | From LOGIN\_HISTORY , bursts indicate brute force or stale credentials. | | **Idle Warehouse Credits Wasted (24h)** | Run operations | Merchant rule | Credits spent while warehouse was on but processing no queries , auto-suspend tuning candidate. | | **Largest Table (GB)** | Run operations | Watch only | From TABLE\_STORAGE\_METRICS. Top tables drive storage cost. | | **Top 10 Slowest Queries** | Customer experience | Watch only | Top 10 Slowest Queries, broken down by row. | | **Active Sessions** | Run operations | Watch only | Description pending editorial review; the signal is live. | | **Active Warehouses** | 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 | | **Credit Burn +50% Week-over-Week** | high | Run operations | Credit burn jumping 50 percent week over week compounds into a painful invoice; the cause is usually one new workload that nobody costed. | 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 | | **Query Error Rate Spike >1% in 1h** | high | Customer experience | Job errors spiking past 1 percent breaks the pipelines that dashboards and models silently depend on. | Report only | | **Query Queue Depth >5 Sustained 10m per Warehouse** | high | Customer experience | Queries queuing behind a saturated warehouse delay every dashboard and job downstream; users experience it as everything being slow. | Candidate remediation | | **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 | | **Active Sessions Climbing (Connection Pool Pressure)** | medium | Run operations | Climbing active sessions exhaust connection pools; when they run out, applications fail loudly and all at once. | 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 | | **Cost per Query Rising >25% Week-over-Week** | medium | Run operations | Cost per query rising 25 percent week over week means efficiency is degrading even if the bill has not caught up yet. | Report only | | **Failed Login Attempts >10 in 24h** | medium | Protect revenue | Failed logins clustering above 10 a day is either an attack or a broken integration credential; both deserve a look the same day. | Report only | | **Idle Warehouse Credits >10% of Total** | medium | Run operations | Warehouses idling while credits accrue is pure waste; auto-suspend settings usually recover it in an afternoon. | Candidate remediation | ### Build your own automated fixes 15 checks report findings on Snowflake 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 **8 read** and **0 write** operations across informationschemaqueryhistorys, snowflakeaccountusagedatabasereplicationusagehistorys, snowflakeaccountusageloginhistorys, snowflakeaccountusagemeteringhistorys, snowflakeaccountusagequeryhistorys, snowflakeaccountusagestorageusages on Snowflake. 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=snowflake) | Resource | Read operations | Write operations | | ----------------------------------------------------- | --------------- | ---------------- | | informationschemaqueryhistorys | 1 | 0 | | snowflakeaccountusagedatabasereplicationusagehistorys | 1 | 0 | | snowflakeaccountusageloginhistorys | 1 | 0 | | snowflakeaccountusagemeteringhistorys | 1 | 0 | | snowflakeaccountusagequeryhistorys | 1 | 0 | | snowflakeaccountusagestorageusages | 1 | 0 | | snowflakeaccountusagetablestoragemetrics | 1 | 0 | | snowflakeaccountusagewarehousemeteringhistorys | 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 Snowflake 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.*