Skip to main content

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.

Checks that GCP Firestore read frequency is being monitored.

​
Why This Matters

Unmonitored infrastructure can degrade silently until services fail. CPU spikes, memory exhaustion, storage depletion, and latency increases are early warning signs of performance issues, resource exhaustion attacks, or misconfiguration. Proactive monitoring is required by SOC 2 (CC7.1) and ISO 27001 (A.12.1.3).

​
What DSALTA Checks

DSALTA connects to your Google Cloud Platform (GCP) environment using read-only API access and evaluates this configuration on every sync cycle. The test result appears in your Data Library → Tests dashboard:
  • Passing — The configuration meets requirements. No action needed.
  • Failing — The configuration does not meet requirements. Follow the remediation steps below.
  • Not configured — The integration is connected but the required service or feature has not been set up yet.
This test runs automatically every 24 hours. If you fix the underlying issue, DSALTA will detect the change on the next sync cycle and update the status to Passing. You can also trigger a manual sync from Settings → Integrations → Google Cloud Platform (GCP).

​
How to Fix

If this test is failing, follow these steps to remediate:
  1. Sign in to the Google Cloud Console and navigate to Monitoring → Alerting → Create policy.
  2. Click Add condition and select the document_reads metric for your Firestore resource.
  3. Configure the threshold to trigger when the metric document reads/second exceeds your expected baseline.
  4. Set the alignment period and evaluation window (e.g., 5 minutes).
  5. Under Notifications, select or create a notification channel (email, Slack, PagerDuty).
  6. Name the alerting policy and click Create policy.
  7. Review query patterns, implement caching, and optimize data models to reduce reads.
  8. Once the alerting policy is active, DSALTA will detect the configuration on the next sync and update the test status to Passing.

​
Frequently Asked Questions

This test runs automatically every 24 hours when the Google Cloud Platform (GCP) integration is connected. You can trigger a manual sync at any time from the integration settings page.
A failing test generates an alert in your DSALTA dashboard. The assigned responsible role receives a notification. Remediate the issue before it affects your compliance posture.
Yes. If this test does not apply to your environment, you can mark it as Not Applicable with a justification. This exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources in your environment. Remediation actions must be performed by your team directly in Google Cloud Platform (GCP).