[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-03。"],[],[],null,["# Monitor usage\n=============\n\nThis page describes how you can monitor your Firestore usage and\nspot potential problems in your app.\n\nUsage dashboard\n---------------\n\nUse the usage dashboards in the Google Cloud console and Firebase console to view\ndocument reads, writes, and deletes over time.\n\n#### Access control\n\nThe usage dashboards require the `monitoring.timeSeries.list` IAM permission.\nThe Project Owner, Editor, and Viewer roles grant this permission. You can also grant this permission\nthrough a [Cloud Monitoring role](https://cloud.google.com/monitoring/access-control#monitoring_2)\nor a [custom role](https://cloud.google.com/iam/docs/creating-custom-roles).\n\n### Database usage dashboard\n\nTo view usage metrics for a Firestore database, open the database **Usage**\npage in the Google Cloud console.\n\n1. In the Google Cloud console, go to the **Databases** page.\n\n [Go to Databases](https://console.cloud.google.com/firestore/databases)\n2. Select the required database from the list of databases.\n\n3. In the navigation menu, click **Usage**.\n\n4. Click the link in the message that appears on the page to view your database usage.\n\n### Aggregated usage dashboard\n\nIf your project has multiple Firestore databases, you can view\naggregated usage metrics in the Google Cloud console or Firebase console. \n\n### Google Cloud console\n\nIn the Google Cloud console, go to the **Project usage** page.\n\n[Go to Google Cloud project project usage](https://console.cloud.google.com/firestore/project-usage)\n\nThe project usage dashboard shows document operations over time as follows:\n\n### Firebase console\n\n[Go to the Firestore usage page (Firebase console)](https://console.firebase.google.com/project/_/firestore/usage/last-24h/reads)\n\n### Usage dashboard and billing reports\n\nThe Firestore usage dashboards in the Firebase and Cloud consoles\nprovide an estimate of usage. They can help you identify spikes in usage.\nHowever, the dashboard is not an exact view of billed operations. Billed usage\nis likely higher. In all cases of discrepancy, the billing report takes\nprecedence over the usage dashboard.\n\nOperations that cause discrepancies between the usage dashboard and billed\nusage include:\n\n- Import and export operations. Reads and writes performed by these operations do not show up in the usage dashboard.\n- No-op verify-only writes. Writes that only verify the existence or non-existence of a document contribute to billed read operations, but they show as \\`UPDATE_NOOP\\` and \\`DELETE_NOOP\\` respectively in the write usage dashboard.\n- No-op writes. Operations that do not result in a change to the database, such as an update that does not change field values or a write to a deleted document may show in the usage dashboard as \\`UPDATE_NOOP\\` or \\`DELETE_NOOP\\`. Even though they show as \\`NOOP\\`, they still contribute to billed operations.\n-\n Collapsed writes. In cases with multiple writes to the same document in quick\n succession, the usage dashboard might collapse multiple writes together and\n count them as one. When billing usage, each write is still counted separately.\n\n\n The usage dashboard also collapses writes for field transforms like server timestamps, numeric increments, and array union operations. For field transforms, the usage dashboard might count multiple operations as a single operation.\n- Queries that return zero results. Queries with zero results incur a cost of one read operation. This usage is billed but does not appear in the usage dashboard.\n- Read operations from [index entries read](/firestore/pricing#index-reads). This usage is billed but does not appear in the usage dashboard. For example, aggregation queries bill for index entries read but this usage does not appear in the usage dashboard.\n\nThe usage dashboard for deletes does not capture automatic expiration operations performed by Time-to-live (TTL) policies. Please refer to the TTL metrics from [Cloud Monitoring](#monitoring-metrics).\n\nSecurity rule usage\n-------------------\n\nAdditionally, the Firebase console provides a Security Rules evaluation\ndashboard, a useful, at-a-glance view of rules invocations. You can supplement\nthis dashboard with detailed analysis in\n[Cloud Monitoring](#cloud-monitoring).\n\n[Go to Rules](https://console.firebase.google.com/project/_/firestore/rules)\n\nCloud Monitoring metrics\n------------------------\n\n[Cloud Monitoring](https://cloud.google.com/monitoring/docs/) collects\nmetrics, events, and metadata from Google Cloud products. The usage\ndashboard in the Firestore console reports the same metrics data. To\nset up custom dashboards and usage alerts, use Cloud Monitoring.\n\nCloud Monitoring includes the following Firestore metrics:\n\nRealtime updates usage\n\n: Use the active connections and snapshot listeners metrics to measure your\n usage of [realtime updates](/firestore/native/docs/query-data/listen).\n\n: Let's say a user opens your app on their phone. The app then connects to\n Firestore and subscribes to 10 queries. This increases\n your metrics by 1 active connection and 10 snapshot listeners.\n\nSampling rate\n\n: The Firestore metrics are sampled every minute, but updates may\n take up to 4 minutes to show up in your dashboards.\n\n### Latency metrics\n\nBackend latency metrics are available through common Google Cloud [firestore](//cloud.google.com//monitoring/api/metrics_gcp_d_h#gcp-firestore) metrics.\n\nFor example, a graph of [p50 latency](https://console.cloud.google.com/monitoring/metrics-explorer;duration=P7D?pageState=%7B%22domainObjectDeprecationId%22:%2212ACB359-342F-4174-8878-0B5FCECCB7E6%22,%22xyChart%22:%7B%22constantLines%22:%5B%5D,%22dataSets%22:%5B%7B%22plotType%22:%22LINE%22,%22targetAxis%22:%22Y1%22,%22timeSeriesFilter%22:%7B%22aggregations%22:%5B%7B%22crossSeriesReducer%22:%22REDUCE_PERCENTILE_50%22,%22groupByFields%22:%5B%5D,%22perSeriesAligner%22:%22ALIGN_DELTA%22%7D%5D,%22apiSource%22:%22DEFAULT_CLOUD%22,%22crossSeriesReducer%22:%22REDUCE_PERCENTILE_50%22,%22filter%22:%22metric.type%3D%5C%22firestore.googleapis.com%2Fapi%2Frequest_latencies%5C%22%20resource.type%3D%5C%22firestore.googleapis.com%2FDatabase%5C%22%20metric.label.%5C%22service%5C%22%3D%5C%22firestore.googleapis.com%5C%22%22,%22groupByFields%22:%5B%5D,%22minAlignmentPeriod%22:%2260s%22,%22perSeriesAligner%22:%22ALIGN_DELTA%22%7D%7D%5D,%22options%22:%7B%22mode%22:%22COLOR%22%7D,%22y1Axis%22:%7B%22label%22:%22%22,%22scale%22:%22LINEAR%22%7D%7D%7D) can be found in the Cloud Console's metrics explorer view.\n\n### Set up a Cloud Monitoring dashboard\n\nTo view a pre-defined dashboard or to set up a dashboard,\nsee [Use the monitoring dashboard](https://cloud.google.com/firestore/docs/use-monitoring-dashboard).\n\nWhat's next\n-----------\n\n- [Learn more about Cloud Monitoring.](https://cloud.google.com/monitoring/docs/)\n- Learn about [best practices for monitoring Firestore performance](https://cloud.google.com/firestore/docs/understand-performance-monitoring)."]]
