> ## 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. # Google Firestore on Vortex IQ > Monitor Google Firestore health, cost and reliability signals, and catch incidents and runaway spend early. Monitor Google Firestore 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=firestore) performance signals automated checks prepared fixes proven workflows API operations ### What you can achieve Capabilities are grouped around merchant outcomes, not API terminology. Keep tracking, access and change under governed control. Find storefront, speed, accessibility and journey problems. Monitor orders, fulfilment, delivery and settlement. Find failures, leaks and risks before they cost sales. ### 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 24 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 Realtime Connections** | Watch only | network/active\_connections - concurrent SDK / realtime connections to the database. | | **Active Snapshot Listeners** | Watch only | network/snapshot\_listeners - Firestore-distinctive realtime listener count (onSnapshot subscriptions). | | **Document Operations per Second (live)** | Watch only | read\_ops\_count + write\_ops\_count + delete\_ops\_count rate from Cloud Monitoring. | | **Document Reads (24h)** | Watch only | document/read\_ops\_count summed over 24h - Firestore bills per document read. | | **Document Writes (24h)** | Watch only | document/write\_ops\_count summed over 24h. | | **Index Builds In Progress** | Merchant rule | Firestore-distinctive - composite indexes in CREATING state. A build stuck many hours blocks the queries that need it. | | **Point-in-Time Recovery Window (hours)** | Alert band 24 / 72 | PITR retention from pointInTimeRecoveryEnablement (7d on Enterprise). No PITR = no rollback path on bad writes. | | **Request Latency p95 >200ms Sustained** | Alert band 0 / 1 | Alerts for Request Latency p95 >200ms Sustained. | | **Stored Bytes** | Watch only | Estimated stored bytes (documents + index entries). Firestore bills per GB-month. | | **Total Document Count** | Watch only | document/count across the database - drives storage cost. | | Signal | Alert behaviour | What it tracks | | ------------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------- | | **API Request Error Rate %** | Alert band 0.1 / 1 | api/request\_count filtered by response\_code != OK over total requests. | | **API Request Error Rate Spike (>1% in 5m)** | Alert band 0.1 / 1 | Alerts for API Request Error Rate Spike (>1% in 5m). | | **Firestore Health Score** | Merchant rule | Composite of latency, error rate, op trend and index health. | | **Index in NEEDS\_REPAIR / ERROR or Build Stuck** | Merchant rule | Alerts for Index in NEEDS\_REPAIR / ERROR or Build Stuck. | | **Indexes in NEEDS\_REPAIR / ERROR** | Merchant rule | Composite indexes in NEEDS\_REPAIR / ERROR state - queries depending on them fail at runtime. | | Signal | Alert behaviour | What it tracks | | ------------------------------------------- | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | **API Request Latency p95 (ms)** | Alert band 50 / 200 | 95th percentile of api/request\_latencies distribution (receive → finish-send). | | **API Request Latency p99 (ms)** | Alert band 100 / 500 | Description pending editorial review; the signal is live. | | **Highest-Latency Request Shapes (top 10)** | Watch only | api/request\_latencies grouped by api\_method + collection group. | | **Read:Write Op Ratio** | Watch only | read\_ops\_count / write\_ops\_count. Firestore-distinctive - a sudden read spike vs writes = unindexed query fan-out or listener amplification. | | **Slow-Query Rate %** | Alert band 1 / 5 | Share of api/request\_latencies samples over 200ms, computed from the metric's raw DISTRIBUTION bucketCounts (Cloud Monitoring, ALIGN\_DELTA/unaggregate | | Signal | Alert behaviour | What it tracks | | ----------------------------------------------------- | --------------- | --------------------------------------------------------------------------------------------------------- | | **Firestore Op Spike vs Ecom Order Rate** | Merchant rule | Firestore bills per read - a read spike with no order spike burns money for nothing. | | **Firestore Products Collection vs Ecom Catalog** | Merchant rule | Firestore-distinctive XC - many headless storefronts keep the catalog in Firestore; drift = sync failure. | | **High-Latency Requests During Checkout Window (5m)** | Merchant rule | High-Latency Requests During Checkout Window (5m), broken down by row. | | **Realtime Connections vs Traffic Burst** | Merchant rule | Realtime Connections vs Traffic Burst, broken down by row. | ### 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 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** 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` #### 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 **5 read** and **0 write** operations across projectdatabas, projectdatabascollectiongroupfields, projectdatabascollectiongroupindexes, projectdatabasoperations, projecttimeserys on Google Firestore. 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=firestore) #### Ready to build your first Google Firestore 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 | | ------------------------------------ | --------------- | ---------------- | | projectdatabas | 1 | 0 | | projectdatabascollectiongroupfields | 1 | 0 | | projectdatabascollectiongroupindexes | 1 | 0 | | projectdatabasoperations | 1 | 0 | | projecttimeserys | 1 | 0 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.