[[["易于理解","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-08-18。"],[[["\u003cp\u003eThis guide provides instructions on how to monitor Filestore instances using Cloud Monitoring, including steps to add metric charts to a dashboard.\u003c/p\u003e\n"],["\u003cp\u003eYou can track various Filestore performance metrics, such as read/write latency, bytes read/written, disk operation counts, and free/used space percentages.\u003c/p\u003e\n"],["\u003cp\u003eThe page explains specific metrics like "free raw capacity percent," "snapshots used bytes," and "used bytes," detailing their relevance to user capacity and performance.\u003c/p\u003e\n"],["\u003cp\u003eInstructions are provided to set up alerts for low disk space on Filestore instances by configuring thresholds and notification channels.\u003c/p\u003e\n"],["\u003cp\u003eThe guide also covers setting up alerts for low backups quota, ensuring users are notified when they are approaching their limits for scheduled or automated backups.\u003c/p\u003e\n"]]],[],null,["# Monitoring instances and quota\n\nThis page shows you how to monitor your Filestore instances and set up\nalerts for low disk space and low backups quota.\n\nYou can monitor Filestore instances using\n[Cloud Monitoring](/monitoring).\n\nBefore you begin\n----------------\n\nBefore you begin, make sure you have access to the following roles:\n\n- Monitoring Viewer\n- Monitoring Editor\n\nTo see how to grant access to these roles, see [Grant access to Cloud Monitoring](/monitoring/access-control#grant-monitoring-access).\n\nAdd a Filestore metric chart to a Cloud Monitoring dashboard\n------------------------------------------------------------\n\nTo see Filestore performance metrics in a Cloud Monitoring\ndashboard, follow these steps:\n\n1. In the Google Cloud console, go to the\n *leaderboard* **Metrics explorer** page:\n\n [Go to **Metrics explorer**](https://console.cloud.google.com/monitoring/metrics-explorer)\n\n \u003cbr /\u003e\n\n If you use the search bar to find this page, then select the result whose subheading is\n **Monitoring**.\n2. Click the **Select a metric** expandable section.\n3. In the **Filter by resource or metric name** field, type `filestore` and select the **Filestore Instance** expandable section.\n4. Select an available metric to view:\n\n ^\\*^Memory-cached operations only occur in Basic tier instances.\n5. Optional configurations:\n\n6. If you want to add more metrics to the chart, click **Add another metric**.\n\n7. Click **Save Chart** to create a dashboard. Alternatively, you can add the\n chart to an existing dashboard.\n\nMetric definitions\n------------------\n\nThe following sections describe certain Filestore-specific metrics\nin detail.\n\n### Free raw capacity percent\n\nThe **[free raw capacity percent](/monitoring/api/metrics_gcp_d_h#gcp-file)**\nmetric represents capacity available to users, not necessarily the available\nraw disk space.\n\nYour instance replicates data to provide durability and to help support\nperformance, resulting in a total storage capacity greater than the\nuser-specified capacity of the instance.\n\nThe **free raw capacity percent** metric represents the percentage of free raw\ncapacity available to users after any replication performed as a function of\ninstance durability or performance.\n\nIf this metric reaches 0%, new data cannot be written to the cluster until more\nfree space becomes available.\n\nFor more information on how to scale instance capacity up or down, see\n[Scale capacity](/filestore/docs/scale).\n\n### Snapshots used bytes\n\nThe **[snapshots used bytes](/monitoring/api/metrics_gcp_d_h#gcp-file)** metric\nrepresents the number of bytes in use by all snapshots, whether internal or\nexternal. This metric is allocated and indexed by share, not instance.\n\n### Used bytes\n\nThe **[used bytes](/monitoring/api/metrics_gcp_d_h#gcp-file)** metric represents the\nraw data written by the user. It doesn't take into account the space required\nfor [inodes](/filestore/docs/scale#inode-usage) and metadata.\n\n### Anticipating capacity\n\nFor a better understanding of an instance's available capacity, we recommend\nmonitoring the available space as well as the written space.\n\nTo see the free space on an instance, use the **[free raw capacity percent](#free-raw-capacity-percent)**\nmetric.\n\nEach file stored on the file share consumes one inode. If the file system runs\nout of inodes, you won't be able to store more files on the file share even\nif you haven't reached the maximum allocated capacity.\n\nTo see the number of inodes in use, use the `df` command. For more information,\nsee [Scale capacity](/filestore/docs/scale) and [Troubleshoot capacity issues](/filestore/docs/capacity-issues).\n\nSet up alerts\n-------------\n\n### Low disk space\n\nTo ensure that your Filestore instances don't run out of free\nspace, we recommend setting up low disk space alerts.\nThis guide uses the **free disk space percent** metric to measure the free disc space for basic instances.\n\nIf you want to measure low disk space for zonal, regional, or enterprise instances, use the following steps to set up two separate alerts using **free disk space percent** and **free raw capacity percent** metrics.\n\n1. In the Google Cloud console, go to the\n *notifications* **Alerting** page:\n\n [Go to **Alerting**](https://console.cloud.google.com/monitoring/alerting)\n\n \u003cbr /\u003e\n\n If you use the search bar to find this page, then select the result whose subheading is\n **Monitoring**.\n2. Click **Create Policy**.\n3. Click the **Select a metric** expandable section.\n4. In the **Filter by resource or metric name** field, type `filestore` and select the **Filestore Instance** expandable section.\n5. Select the **Nfs** active metric category.\n6. Select the metric **Free disk space percent**.\n7. Click **Apply**.\n8. In the **Add filters** section, click **Add a filter**.\n9. Click the **Filter** expandable section and select **instance_name**.\n10. In the **Value** field, enter the Filestore instance name for which you want to receive alerts.\n11. Click **Done**.\n\n For more information about filtering Cloud Monitoring metrics, see\n [Filtering](/monitoring/charts/metrics-selector#filter-option).\n12. In the **Transform data** section, specify the **Rolling window** and\n **Rolling window function** . Indicate whether you want to include a\n secondary data transformation and click **Next**.\n\n13. In the **Configure alert trigger** window, choose a condition type.\n\n14. Set the following specifications:\n\n You can test the alert by setting a low limit and seeing whether the alert\n gets triggered.\n\n For more information, see [Default create alerting policy flow](/monitoring/alerts/using-alerting-ui#default).\n15. Enter any advanced options.\n\n16. In the **Condition name** field, enter a name for the condition.\n\n17. Click **Next**.\n\n18. In the **Configure notifications and finalize alert** window, indicate\n which notification channels you want to use.\n\n For information on how to create new channels, see [Manage notification\n channels](/monitoring/support/notification-options).\n19. In the **Incident autoclose duration** menu, select the duration you want\n to use.\n\n20. In the **Policy user labels** section, indicate the labels you want to use.\n\n21. In the **Documentation** section, add any documentation you want to include\n such as instructions on how to address the issue.\n\n22. In the **Alert policy name** field, enter an alert policy name and click\n **Next**.\n\n23. Click **Create policy**.\n\n### Low backups quota\n\nIf you are scheduling or automating backups creation for your\nFilestore instances, you should set up alerts for when you're\nrunning low on backups quota.\n\n1. In the Google Cloud console, go to the\n *notifications* **Alerting** page:\n\n [Go to **Alerting**](https://console.cloud.google.com/monitoring/alerting)\n\n \u003cbr /\u003e\n\n If you use the search bar to find this page, then select the result whose subheading is\n **Monitoring**.\n2. Click **Create Policy**.\n3. Click the **Select a metric** expandable section.\n4. In the **Filter by resource or metric name** field, type `quota` and select the **Consumer quota** expandable section.\n5. Select the **Quota** active metric category.\n6. Select the metric **Allocation quota usage**.\n7. Click **Apply**.\n8. In the **Add filters** section, click **Add Filter**.\n9. Click the **Filter** expandable section and select **quota_metric**.\n10. In the **Value** field, enter `file.googleapis.com/backups-per-region`.\n11. Click **Done**.\n12. Optional: To add another filter, click **Add filter** and repeat the\n process.\n\n For more information about filtering Cloud Monitoring metrics, see\n [Filtering](/monitoring/charts/metrics-selector#filter-option).\n13. In the **Transform data** section, specify the **Rolling window** and\n **Rolling window function** . Indicate whether you want to include a\n secondary data transformation and click **Next**.\n\n14. In the **Configure alert trigger** window, choose a condition type.\n\n15. Set the following specifications:\n\n You can test the alert by setting a low limit and seeing whether the alert\n gets triggered.\n\n For more information, see [Default create alerting policy flow](/monitoring/alerts/using-alerting-ui#default).\n16. Enter any advanced options.\n\n17. In the **Condition name** field, enter a name for the condition.\n\n18. Click **Next**.\n\n19. In the **Configure notifications and finalize alert** window, indicate\n which notification channels you want to use.\n\n For information on how to create new channels, see [Manage notification\n channels](/monitoring/support/notification-options).\n20. In the **Incident autoclose duration** menu, select the duration you want\n to use.\n\n21. In the **Policy user labels** section, indicate the labels you want to use.\n\n22. In the **Documentation** section, add any documentation you want to include\n such as instructions on how to address the issue, for example, \"Delete older\n backups\" or \"Request additional quota\".\n\n23. In the **Alert policy name** field, enter an alert policy name and click\n **Next**.\n\n24. Click **Create policy**.\n\nWhat's next\n-----------\n\n- [Request a quota increase](/filestore/docs/requesting-quota-increases).\n- [Understand capacity errors](/filestore/docs/known-issues#capacity_errors_before_reaching_full_provisioned_capacity).\n- [Optimize and test instance performance](/filestore/docs/performance).\n- [Scale capacity](/filestore/docs/scale)."]]
