31
performance signals
14
automated checks
Build your own
automated fixes
Ready to build yours
workflows
7
API operations
- Overview
- Monitor (31)
- Audit (14)
- Automate
What you can achieve
Capabilities are grouped around merchant outcomes, not API terminology.Protect revenue
Find failures, leaks and risks before they cost sales.
Run operations
Monitor orders, fulfilment, delivery and settlement.
Control risk and change
Keep tracking, access and change under governed control.
Customer experience
Find storefront, speed, accessibility and journey problems.
Grow revenue
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.1
Connect
Authorise the source. Scopes are shown before access is granted.
2
Monitor
Watch the signals against your own baselines, not universal defaults.
3
Detect
Run checks and gather evidence specific to your store.
4
Recommend
Explain what happened, why it matters and the proposed action.
5
Approve
You review scope, risk and reversibility before anything changes.
6
Execute
Apply through governed connector operations.
7
Verify
Confirm the intended result and keep the receipt.
Monitor performance
31 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.Run operations (16 signals)
Run operations (16 signals)
| Signal | Alert behaviour | What it tracks |
|---|---|---|
| Active Datasets | Watch only | Count from datasets.list. |
| BigQuery Health Score | Merchant rule | Description pending editorial review; the signal is live. |
| Bytes Scanned (24h) | Merchant rule | SUM(total_bytes_processed) from INFORMATION_SCHEMA.JOBS. BigQuery-defining - on-demand billing is per byte scanned (~$6.25/TiB). This IS the spend sig |
| Bytes-Scanned Cost +50% Week-over-Week | Merchant rule | BigQuery-distinctive - un-pruned / runaway query scanning a giant un-partitioned table is the #1 cost surprise. |
| Concurrent Query Jobs | Merchant rule | RUNNING jobs from jobs.list - interactive concurrency quota defaults ~100/project. Approaching cap = queries queue or fail. |
| Estimated On-Demand Query Cost (24h) | Merchant rule | total_bytes_billed × on-demand rate ($6.25/TiB default; first 1 TiB/month free). Capacity-priced projects show slot cost instead. |
| Largest Table (GB) | Watch only | From INFORMATION_SCHEMA.TABLE_STORAGE active_logical_bytes. Top tables drive storage cost. |
| Last Table Snapshot Age (hours) | Alert band 24 / 72 | BigQuery time-travel retains 7 days by default; table snapshots / scheduled exports are the explicit backup. Reflects newest snapshot age. |
| Long-Term Storage % | Watch only | long_term_bytes ÷ (active + long_term). Higher = more tables untouched 90d, billed at ~half rate - informational cost lever. |
| Pending Jobs (waiting for slots) | Merchant rule | Jobs in PENDING state from jobs.list - sustained pending = reservation under-provisioned or concurrency cap hit. |
| Query Jobs per Hour (live) | Watch only | Count of QUERY jobs from INFORMATION_SCHEMA.JOBS in the last hour. Baseline-relative, no absolute band. |
| Reservation Slot Saturation (>90% sustained) | Alert band 70 / 90 | Alerts for Reservation Slot Saturation (>90% sustained). |
| Slot Utilisation % | Alert band 70 / 90 | slots/allocated ÷ reservation capacity (Cloud Monitoring). Sustained 100% on a reservation = queueing; on-demand has no slot cap to hit. BigQuery-dist |
| Slot-ms Consumed (24h) | Watch only | SUM(total_slot_ms) from INFORMATION_SCHEMA.JOBS - the capacity-pricing cost anchor (vs bytes for on-demand). |
| Streaming Buffer Lag (s) | Alert band 1 / 10 | Streaming-insert buffer flush lag - high lag means freshly streamed rows aren’t queryable yet (ingest pipeline backpressure). |
| Top 10 Most Expensive Queries | Watch only | Ordered by total_bytes_processed from INFORMATION_SCHEMA.JOBS. The optimisation hit-list - add partitioning / clustering / pruning here. |
Customer experience (6 signals)
Customer experience (6 signals)
| Signal | Alert behaviour | What it tracks |
|---|---|---|
| Query Cache Hit Rate % | Alert band 95 / 80 | Share of jobs where cache_hit = true in INFORMATION_SCHEMA.JOBS - cached results are free, so a rising cache rate cuts cost. BigQuery-distinctive. |
| Query Latency p50 (ms) | Watch only | Median (end_time - start_time) from INFORMATION_SCHEMA.JOBS. |
| Query Latency p95 (ms) | Alert band 50 / 200 | BigQuery analytics queries measured in seconds - threshold reflects warehouse use case, not OLTP. |
| Query Latency p99 (ms) | Alert band 100 / 500 | Description pending editorial review; the signal is live. |
| Slow-Query Rate % | Alert band 1 / 5 | Share of query jobs with duration > 5s in INFORMATION_SCHEMA.JOBS. |
| Top 10 Slowest Queries | Watch only | Top 10 Slowest Queries, broken down by row. |
Protect revenue (4 signals)
Protect revenue (4 signals)
| Signal | Alert behaviour | What it tracks |
|---|---|---|
| BigQuery Event Ingest vs Ecom Orders | Merchant rule | Fivetran / Dataflow ingest stall while orders flow = analytics blind spot; dashboards silently go stale. |
| BigQuery Query Spike vs Ecom Order Rate | Merchant rule | Description pending editorial review; the signal is live. |
| Bytes-Scanned Cost vs Ecom Order Volume | Merchant rule | BigQuery-distinctive XC - on-demand spend should track ecom volume (more data to analyse = more bytes). Divergence = wasted scan cost. |
| Expensive Queries During Checkout Window | Merchant rule | Expensive Queries During Checkout Window, broken down by row. |
Control risk and change (3 signals)
Control risk and change (3 signals)
| Signal | Alert behaviour | What it tracks |
|---|---|---|
| Job Error Rate % | Alert band 0.1 / 1 | Share of jobs with error_result set in INFORMATION_SCHEMA.JOBS (quota exceeded, permission, syntax, resources). |
| Job Error Rate Spike (>1% in 1h) | Alert band 0.1 / 1 | Alerts for Job Error Rate Spike (>1% in 1h). |
| Quota-Exceeded Errors (24h) | Merchant rule | Jobs failing with quotaExceeded reason - concurrency / bytes-billed / API quota hit. BigQuery-distinctive failure mode. |
Grow revenue (2 signals)
Grow revenue (2 signals)
| Signal | Alert behaviour | What it tracks |
|---|---|---|
| Bytes Scanned by User (7d) | Watch only | GROUP BY user_email (hashed) from INFORMATION_SCHEMA.JOBS. Surfaces the top spenders for cost attribution. |
| Total Storage (TB) | Alert band 70 / 90 | Sum of active + long-term logical bytes across datasets (tables.get / TABLE_STORAGE). 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.Connection pool saturation above 90%
Connection pool saturation above 90%
Severity critical · Outcome Customer experience · Fix status Report onlyAt 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-001Disk usage above 90%
Disk usage above 90%
Severity critical · Outcome Run operations · Fix status Report onlyA 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-002Query error rate above 1% in last 5 minutes
Query error rate above 1% in last 5 minutes
Severity critical · Outcome Run operations · Fix status Report onlyMore 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-001Bytes Scanned +50% Week-over-Week
Bytes Scanned +50% Week-over-Week
Severity high · Outcome Run operations · Fix status Report onlyBytes scanned jumping 50 percent week over week is the leading indicator of a runaway query or a new unpartitioned workload; costs follow within the billing cycle.Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.Reference:
BQ-COST-001Job Error Rate Spike >1% in 1h
Job Error Rate Spike >1% in 1h
Severity high · Outcome Customer experience · Fix status Report onlyJob 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:
BQ-PERF-004Last successful backup older than 72 hours
Last successful backup older than 72 hours
Severity high · Outcome Run operations · Fix status Report onlyIf 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-001Replication lag above 10 seconds
Replication lag above 10 seconds
Severity high · Outcome Run operations · Fix status Report onlyAnything 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-001Reservation Slot Utilisation >90% Sustained with Jobs Pending
Reservation Slot Utilisation >90% Sustained with Jobs Pending
Severity high · Outcome Run operations · Fix status Report onlySustained reservation-slot saturation with jobs pending means workloads are queuing every day; capacity or scheduling needs a decision.Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.Reference:
BQ-CAP-003Slow-query rate above 5% of total
Slow-query rate above 5% of total
Severity high · Outcome Customer experience · Fix status Report onlyMore 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-002p95 query latency above 200ms sustained 15m
p95 query latency above 200ms sustained 15m
Severity high · Outcome Customer experience · Fix status Report onlyOne 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 customerVortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.Reference:
DB-PERF-001Buffer / cache hit rate below 80%
Buffer / cache hit rate below 80%
Severity medium · Outcome Run operations · Fix status Report onlyMore 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-001Quota-Exceeded Errors Detected (>0 in 24h)
Quota-Exceeded Errors Detected (>0 in 24h)
Severity medium · Outcome Customer experience · Fix status Report onlyQuota-exceeded errors mean jobs are being refused outright; whatever depends on them is already stale.Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.Reference:
BQ-PERF-005Single Query Scanning >1 TiB (un-partitioned / un-pruned)
Single Query Scanning >1 TiB (un-partitioned / un-pruned)
Severity medium · Outcome Run operations · Fix status Report onlyA single query scanning over a tebibyte almost always means a missing partition filter; one WHERE clause can cut its cost by orders of magnitude.Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.Reference:
BQ-COST-002Query Cache Hit Rate Below 50% (cost lever unused)
Query Cache Hit Rate Below 50% (cost lever unused)
Severity low · Outcome Run operations · Fix status Report onlyCache hit rate below half means the warehouse is recomputing answers it already produced; free savings are being left off.Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.Reference:
BQ-COST-003Build 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 6 read and 1 write operations across projectdatasettables, projectjobs, projectdatasets, projectquerys, projecttimeserys on Google BigQuery. 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 workflowReady to build your first Google BigQuery 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.Browse the operations you can build with
Browse the operations you can build with
| Resource | Read operations | Write operations |
|---|---|---|
| projectdatasettables | 2 | 0 |
| projectjobs | 2 | 0 |
| projectdatasets | 1 | 0 |
| projectquerys | 0 | 1 |
| projecttimeserys | 1 | 0 |