Firebase 및 Cloud Console의 Firestore 사용량 대시보드는 예상 사용량을 제공합니다. 이는 사용량 급증을 식별하는 데 도움이 됩니다.
하지만 대시보드는 청구 작업의 정확한 뷰가 아닙니다. 청구 사용량이 더 높을 수 있습니다. 불일치가 발생하는 경우 언제나 청구 보고서가 사용량 대시보드보다 우선합니다.
사용량 대시보드와 청구 사용량 사이에 불일치를 일으킬 수 있는 작업은 다음과 같습니다.
가져오기 및 내보내기 작업 이러한 작업으로 수행되는 읽기 및 쓰기는 사용량 대시보드에 표시되지 않습니다.
노옵스(no-ops) 확인 전용 쓰기: 문서의 존재 여부만 확인하는 쓰기는 청구 대상 읽기 작업에 속하지만 쓰기 사용량 대시보드에 각각 'UPDATE_NOOP' 및 'DELETE_NOOP'로 표시됩니다.
노옵스(no-ops) 쓰기: 필드 값을 변경하지 않는 업데이트 또는 삭제된 문서에 대한 쓰기 등 데이터베이스가 변경되지 않는 작업은 사용량 대시보드에 'UPDATE_NOOP' 또는 'DELETE_NOOP'로 표시될 수 있습니다. 'NOOP'로 표시되더라도 청구 대상 작업에 속합니다.
축소된 쓰기: 동일한 문서에 여러 번의 쓰기 작업이 연속으로 빠르게 발생하는 경우 사용량 대시보드는 여러 번의 쓰기를 한 번의 쓰기로 축소하여 계산할 수 있습니다. 청구 사용량에서 각각의 쓰기는 별도로 계산됩니다.
또한 사용량 대시보드는 서버 타임스탬프, 숫자 증가, 배열 통합 작업과 같은 필드 변환에 대한 쓰기도 축소합니다. 사용량 대시보드는 필드 변환의 여러 작업을 단일 작업으로 계산할 수 있습니다.
0개의 결과를 반환하는 쿼리: 결과가 0개인 쿼리는 읽기 작업 1회에 대한 비용이 발생합니다. 이 사용량에는 요금이 청구되지만 사용량 대시보드에는 표시되지 않습니다.
색인 항목 읽기의 읽기 작업. 이 사용량에는 요금이 청구되지만 사용량 대시보드에는 표시되지 않습니다. 예를 들어 집계 쿼리는 읽은 색인 항목에 대해 요금이 청구되지만 이 사용량은 사용량 대시보드에 표시되지 않습니다.
삭제의 사용량 대시보드에는 TTL(수명) 정책에서 수행되는 자동 만료 작업이 캡처되지 않습니다. Cloud Monitoring의 TTL 측정항목을 참조하세요.
보안 규칙 사용
또한 Firebase Console은 규칙 호출을 한 눈에 볼 수 있는 유용한 보안 규칙 평가 대시보드를 제공합니다. Cloud Monitoring의 자세한 분석으로 이 대시보드를 보완할 수 있습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[],[],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)."]]
