> ## 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. [Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=snowflake) performance signals automated checks prepared fixes proven workflows API operations ### What you can achieve Capabilities are grouped around merchant outcomes, not API terminology. Monitor orders, fulfilment, delivery and settlement. Find storefront, speed, accessibility and journey problems. Find failures, leaks and risks before they cost sales. Keep tracking, access and change under governed control. Improve discovery, conversion, campaigns and repeat purchase. ### From connection to verified outcome The controlled sequence every capability follows. Nothing changes a connected system without the approval step. Authorise the source. Scopes are shown before access is granted. Watch the signals against your own baselines, not universal defaults. Run checks and gather evidence specific to your store. Explain what happened, why it matters and the proposed action. You review scope, risk and reversibility before anything changes. Apply through governed connector operations. Confirm the intended result and keep the receipt. 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. ### Monitor performance 29 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system. | Signal | Alert behaviour | What it tracks | | ---------------------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------- | | **Active Sessions** | Watch only | Description pending editorial review; the signal is live. | | **Active Warehouses** | Watch only | Description pending editorial review; the signal is live. | | **Avg Cost per Query (\$)** | Merchant rule | (credits \* \$/credit) / query\_count. Rising = inefficient queries OR more results returned per query. | | **Credit Burn +50% Week-over-Week** | Merchant rule | Snowflake-distinctive , runaway query / scheduled job overrun is the #1 cost surprise. | | **Credits Burned (24h)** | Merchant rule | From METERING\_HISTORY. Snowflake-defining , credits = dollars burned in compute time. | | **Credits by Warehouse (7d)** | Watch only | Per-warehouse credit consumption. Drives sizing + scheduling decisions. | | **Cross-Account Replication Lag (s)** | Alert band 1 / 10 | Description pending editorial review; the signal is live. | | **Idle Warehouse Credits Wasted (24h)** | Merchant rule | Credits spent while warehouse was on but processing no queries , auto-suspend tuning candidate. | | **Largest Table (GB)** | Watch only | From TABLE\_STORAGE\_METRICS. Top tables drive storage cost. | | **Last Snapshot Age (hours)** | Alert band 24 / 72 | Snowflake auto-snapshots via Time Travel (default 1d, up to 90d on Enterprise). This reflects Time Travel retention floor. | | **Queries per Hour (live)** | Watch only | Description pending editorial review; the signal is live. | | **Snowflake Health Score** | Merchant rule | Description pending editorial review; the signal is live. | | **Warehouse Queueing Sustained (>5 queries queued)** | Alert band 70 / 90 | Alerts for Warehouse Queueing Sustained (>5 queries queued). | | **Warehouse Saturation %** | Alert band 70 / 90 | running\_queries / max\_concurrency\_level per warehouse , sustained 100% indicates need to upsize or multi-cluster. | | Signal | Alert behaviour | What it tracks | | --------------------------------------- | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Avg Query Queue Depth per Warehouse** | Merchant rule | From QUEUED\_PROVISIONING\_TIME + QUEUED\_OVERLOAD\_TIME in QUERY\_HISTORY. Snowflake-distinctive , sustained queue = warehouse undersized. | | **Query Latency p50 (ms)** | Watch only | Description pending editorial review; the signal is live. | | **Query Latency p95 (ms)** | Alert band 50 / 200 | Snowflake p95 measured in seconds, not ms , threshold reflects analytics use case. | | **Query Latency p99 (ms)** | Alert band 100 / 500 | Description pending editorial review; the signal is live. | | **Slow-Query Rate %** | Alert band 1 / 5 | Description pending editorial review; the signal is live. | | **Top 10 Slowest Queries** | Watch only | Top 10 Slowest Queries, broken down by row. | | **Warehouse Cache Hit Rate %** | 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 SS | | Signal | Alert behaviour | What it tracks | | ------------------------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | **Credit Burn vs Ecom Order Volume** | Merchant rule | Snowflake-distinctive XC , credit burn should track ecom volume (more data to analyse = more credits). Divergence = cost inefficiency. | | **Failed Logins (24h)** | Merchant rule | From LOGIN\_HISTORY , bursts indicate brute force or stale credentials. | | **Slow Analytics Queries During Checkout Window** | Merchant rule | Slow Analytics Queries During Checkout Window, broken down by row. | | **Snowflake Event Ingest vs Ecom Orders** | Merchant rule | Description pending editorial review; the signal is live. | | **Snowflake QPS Spike vs Ecom Order Rate** | Merchant rule | Description pending editorial review; the signal is live. | | Signal | Alert behaviour | What it tracks | | -------------------------------------- | ------------------ | --------------------------------------------------------- | | **Query Error Rate %** | Alert band 0.1 / 1 | Description pending editorial review; the signal is live. | | **Query Error Rate Spike (>1% in 1h)** | Alert band 0.1 / 1 | Alerts for Query Error Rate Spike (>1% in 1h). | | Signal | Alert behaviour | What it tracks | | --------------------- | ------------------ | ------------------------------------------------------------------------------------------- | | **Storage Used (TB)** | Alert band 70 / 90 | From STORAGE\_USAGE table (1.5hr latency). Storage is cost-anchored , growth = bill growth. | ### 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. Open a check for the detail. **Severity** critical · **Outcome** Customer experience · **Fix status** Report only 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, including new customer sessions and checkout, starts failing, not just slowing down. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `DB-CAP-001` **Severity** critical · **Outcome** Run operations · **Fix status** Report only 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 slower. There is very little runway left at 90%. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `DB-CAP-002` **Severity** critical · **Outcome** Run operations · **Fix status** Report only 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 silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `DB-ERR-001` **Severity** high · **Outcome** Run operations · **Fix status** Report only Credit burn jumping 50 percent week over week compounds into a painful invoice; the cause is usually one new workload that nobody costed. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `SN-COST-001` **Severity** high · **Outcome** Run operations · **Fix status** Report only 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 would be unrecoverable in a real incident, not just delayed. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `DB-BAK-001` **Severity** high · **Outcome** Customer experience · **Fix status** Report only Job errors spiking past 1 percent breaks the pipelines that dashboards and models silently depend on. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `SN-PERF-004` **Severity** high · **Outcome** Customer experience · **Fix status** Candidate remediation Queries queuing behind a saturated warehouse delay every dashboard and job downstream; users experience it as everything being slow. A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided. Reference: `SN-PERF-005` **Severity** high · **Outcome** Run operations · **Fix status** Report only 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 replica is also that far behind on failover, which is a bigger problem than the staleness alone. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `DB-REP-001` **Severity** high · **Outcome** Customer experience · **Fix status** Report only 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 database is paying the slow-query cost, not just an unlucky occasional request. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `DB-PERF-002` **Severity** high · **Outcome** Customer experience · **Fix status** Report only 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 database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `DB-PERF-001` **Severity** medium · **Outcome** Run operations · **Fix status** Report only Climbing active sessions exhaust connection pools; when they run out, applications fail loudly and all at once. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `SN-CAP-003` **Severity** medium · **Outcome** Run operations · **Fix status** Report only 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 one obvious failure. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `DB-CACHE-001` **Severity** medium · **Outcome** Run operations · **Fix status** Report only Cost per query rising 25 percent week over week means efficiency is degrading even if the bill has not caught up yet. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `SN-COST-003` **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only Failed logins clustering above 10 a day is either an attack or a broken integration credential; both deserve a look the same day. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `SN-SEC-001` **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation Warehouses idling while credits accrue is pure waste; auto-suspend settings usually recover it in an afternoon. A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided. Reference: `SN-COST-002` #### Build your own automated fixes Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 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 **over 13,000 operations across more than 200 connectors** to automate the work in your own words. Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=snowflake) #### 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. | 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.