> ## Documentation Index
> Fetch the complete documentation index at: https://help.dsalta.com/llms.txt
> Use this file to discover all available pages before exploring further.

# GCP Firestore write frequency should be monitored

> Checks that GCP Firestore write frequency is being monitored.

Checks that GCP Firestore write frequency is being monitored.

## About

When you connect Google Cloud Platform (GCP) to DSALTA, the platform retrieves the list of resources in your environment using read-only API access. DSALTA then checks whether this configuration is in place. If it is not, DSALTA activates this check so you can remediate it.

## Why This Matters

Infrastructure that is not monitored fails silently until it impacts users. Tracking key metrics — and alerting when they cross a threshold — lets you act before a small issue becomes an outage. Proactive monitoring is required by SOC 2 and ISO 27001.

## How to Fix

**Before you begin**

* Ensure you have the **Monitoring Editor** role on the GCP project.
* Confirm that you have Firestore resources for which you want to create the alert.

**Create the Cloud Monitoring alert**

1. Sign in to the [Google Cloud Console](https://console.cloud.google.com/) and navigate to **Monitoring → Alerting**.
2. Click **Create policy**, then **Add condition**.
3. Select the **document\_write\_count** metric for your Firestore resource.
4. Configure the threshold to alert when writes exceed your expected baseline, and set the alignment and evaluation window.
5. Under **Notifications**, select or create a notification channel (email, Slack, or PagerDuty).
6. Name the alerting policy and click **Create policy**.

Once the alerting policy is active for **document\_write\_count**, DSALTA retrieves the change on the next sync and sets the check status to **Passing**.

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="How often does this check run?">
    This check runs automatically every 24 hours while the Google Cloud Platform (GCP) integration is connected. You can also trigger a manual sync from **Integrations** in the sidebar.
  </Accordion>

  <Accordion title="What happens if it keeps failing?">
    A failing check appears in your **Data Library → Tests** dashboard. Work through the steps above; once the underlying configuration is fixed, the status updates automatically on the next sync.
  </Accordion>

  <Accordion title="Can I exclude this check?">
    Yes. If it does not apply to your environment, mark it as **Not Applicable** with a justification. The exclusion is documented for auditors.
  </Accordion>

  <Accordion title="Does DSALTA change my Google Cloud Platform (GCP) configuration?">
    No. DSALTA uses **read-only API access** and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Google Cloud Platform (GCP).
  </Accordion>
</AccordionGroup>