Migrate API quotas from global metrics to regional metrics
Stay organized with collections
Save and categorize content based on your preferences.
This document describes the quota metrics for regional APIs and the limit
for each metric. It also describes how to update your Cloud Monitoring
dashboards, alerting policies and queries to use the regional metrics.
Regional API quota metrics
Compute Engine regional APIs that used the global quota metrics are
migrated to use the regional metrics. Global APIs continue to use the global
metrics and quota limits. See API rate limits for global metrics.
The following metrics don't have any global APIs. If you are referencing these
metrics in the Cloud Monitoring dashboards, alerts, or queries, you must
migrate these metrics to the corresponding regional metrics.
When you migrate from the existing API quota metrics to the regional API quota
metrics, you must manually update the Cloud Monitoring dashboards, alerts, and
queries to use regional metrics.
Update Cloud Monitoring dashboard to use the regional metrics
To change an alerting policy that monitors a global API quota metric to a
regional metric, do the following:
In the Google Cloud console, select Monitoring.
In the navigation pane, select Dashboards.
Select the dashboard that you want to edit to use a regional metric.
Click Edit dashboard.
Edit the filter that corresponds to the metric that you want to migrate:
In the Filter field, select quota_metric.
In the Comparator field, select =~.
In the Value field, specify the metric name for the regional API quota.
For example, the filter quota_metric =~ compute.googleapis.com/read_requests.*
uses a regular expression to match all time-series data that uses the quota
metric compute.googleapis.com/read_requests.*.
Optional: If you want to view the usage of quota per region,
expand the Grouped header and select location in the
Group by field.
Click Close editor.
Update Cloud Monitoring alerting policies to use the regional API quota metrics
To change an alerting policy that monitors a global API quota metric to a
regional metric, do the following:
In the Google Cloud console, select Monitoring.
In the navigation pane, select Alerting.
The Alerting page displays panes that list summary information, incidents,
and alerting policies.
Click the alerting policy that you want to edit to use a regional metric.
Click Edit to modify the policy.
Edit the filter that corresponds to the metric that you want to migrate:
In the Filter field, select quota_metric.
In the Comparator field, select =~.
In the Value field, specify the metric name for the regional API quota.
For example, the filter quota_metric =~ compute.googleapis.com/read_requests.*
uses a regular expression to match all time-series data that uses the quota
metric compute.googleapis.com/read_requests.*.
Optional: If you want per-region alert for the regional metric,
expand the Across time series header and select location in the
Time series group by field.
Click Save policy.
Update Cloud Monitoring queries to use the regional quota metrics
To change the quota metric in an MQL-based alerting policy or a chart in
a dashboard, use the Query Editor and edit the query filter. See
Using the Query Editor.
Open the Query Editor and edit the filter for query metric as shown in the following
example:
Optionally, you can group the alert based on a location by using the group-by
operation:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[[["\u003cp\u003eCompute Engine regional APIs are migrating from global to regional quota metrics, while global APIs continue to use global metrics and limits.\u003c/p\u003e\n"],["\u003cp\u003eSeveral global API quota metrics are being replaced by corresponding regional metrics, requiring updates to Cloud Monitoring setups.\u003c/p\u003e\n"],["\u003cp\u003eSome metrics do not have global APIs, therefore you must migrate them to their regional counterpart.\u003c/p\u003e\n"],["\u003cp\u003eUpdating Cloud Monitoring dashboards, alerting policies, and queries to use regional metrics involves modifying filters to specify the new regional metric names, such as \u003ccode\u003ecompute.googleapis.com/read_requests_per_region\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eSome metrics don't have regional or zonal APIs, so no migration is needed for them.\u003c/p\u003e\n"]]],[],null,["*** ** * ** ***\n\nThis document describes the quota metrics for regional APIs and the limit\nfor each metric. It also describes how to update your Cloud Monitoring\ndashboards, alerting policies and queries to use the regional metrics.\n\nRegional API quota metrics\n\nCompute Engine regional APIs that used the global quota metrics are\nmigrated to use the regional metrics. Global APIs continue to use the global\nmetrics and quota limits. See [API rate limits for global metrics](/compute/api-quota#api-rate-limits-global).\n\nFor more information about the methods that use the regional metrics and the\nlimits, see [API rate limits for regional metrics](/compute/api-quota#api-rate-limits-regional).\n\nThe following table lists all metrics that are migrated from the global API quota\nmetrics to regional metrics:\n\n| **Global API quota metric** | **Regional API quota metric** |\n|---------------------------------------------------------|--------------------------------------------------------------------|\n| `compute.googleapis.com/default` | `compute.googleapis.com/default_per_region` |\n| `compute.googleapis.com/read_requests` | `compute.googleapis.com/read_requests_per_region` |\n| `compute.googleapis.com/list_requests` | `compute.googleapis.com/list_requests_per_region` |\n| `compute.googleapis.com/operation_read_requests` | `compute.googleapis.com/operation_read_requests_per_region` |\n| `compute.googleapis.com/heavy_weight_read_requests` | `compute.googleapis.com/heavy_weight_read_requests_per_region` |\n| `compute.googleapis.com/heavy_weight_write_requests` | `compute.googleapis.com/heavy_weight_write_requests_per_region` |\n| `compute.googleapis.com/global_resource_write_requests` | `compute.googleapis.com/global_resource_write_requests_per_region` |\n\nThe following metrics don't have any global APIs. If you are referencing these\nmetrics in the Cloud Monitoring dashboards, alerts, or queries, you *must*\nmigrate these metrics to the corresponding regional metrics.\n\n| **Global API quota metric** | **Regional API quota metric** |\n|--------------------------------------------------------------|-------------------------------------------------------------------------|\n| `compute.googleapis.com/simulate_maintenance_event_requests` | `compute.googleapis.com/simulate_maintenance_event_requests_per_region` |\n| `compute.googleapis.com/instance_list_referrers_requests` | `compute.googleapis.com/instance_list_referrers_requests_per_region` |\n| `compute.googleapis.com/get_serial_port_output_requests` | `compute.googleapis.com/get_serial_port_output_requests_per_region` |\n| `compute.googleapis.com/network_endpoint_write_requests` | `compute.googleapis.com/network_endpoint_write_requests_per_region` |\n| `compute.googleapis.com/network_endpoint_list_requests` | `compute.googleapis.com/network_endpoint_list_requests_per_region` |\n\nThe following metrics don't have any regional or zonal APIs. Therefore, no\nchanges are required for regional API quota migration.\n\n- `compute.googleapis.com/project_set_common_instance_metadata_requests`\n- `compute.googleapis.com/license_insert_requests`\n\nMigrate Cloud Monitoring metrics\n\nWhen you migrate from the existing API quota metrics to the regional API quota\nmetrics, you must manually update the Cloud Monitoring dashboards, alerts, and\nqueries to use regional metrics.\n\nUpdate Cloud Monitoring dashboard to use the regional metrics\n\nTo change an alerting policy that monitors a global API quota metric to a\nregional metric, do the following:\n\n1. In the Google Cloud console, select **Monitoring**.\n2. In the navigation pane, select **Dashboards**.\n3. Select the dashboard that you want to edit to use a regional metric.\n4. Click **Edit dashboard**.\n5. Edit the filter that corresponds to the metric that you want to migrate:\n\n 1. In the **Filter** field, select `quota_metric`.\n 2. In the **Comparator** field, select `=~`.\n 3. In the **Value** field, specify the metric name for the regional API quota.\n For example, the filter `quota_metric =~ compute.googleapis.com/read_requests.*`\n uses a regular expression to match all time-series data that uses the quota\n metric `compute.googleapis.com/read_requests.*`.\n\n For more information about the metrics, See [API rate limits for regional metrics](/compute/api-quota#api-rate-limits-regional).\n 4. Click **Done** to save changes.\n\n 5. Optional: If you want to view the usage of quota per region,\n expand the **Grouped** header and select `location` in the\n **Group by** field.\n\n6. Click **Close editor**.\n\nUpdate Cloud Monitoring alerting policies to use the regional API quota metrics\n\nTo change an alerting policy that monitors a global API quota metric to a\nregional metric, do the following:\n\n1. In the Google Cloud console, select **Monitoring**.\n2. In the navigation pane, select **Alerting**. The Alerting page displays panes that list summary information, incidents, and alerting policies.\n3. Click the alerting policy that you want to edit to use a regional metric.\n4. Click **Edit** to modify the policy.\n5. Edit the filter that corresponds to the metric that you want to migrate:\n\n 1. In the **Filter** field, select `quota_metric`.\n 2. In the **Comparator** field, select `=~`.\n 3. In the **Value** field, specify the metric name for the regional API quota.\n For example, the filter `quota_metric =~ compute.googleapis.com/read_requests.*`\n uses a regular expression to match all time-series data that uses the quota\n metric `compute.googleapis.com/read_requests.*`.\n\n For more information about the metrics, see [API rate limits for regional metrics](/compute/api-quota#api-rate-limits-regional).\n 4. Click **Done** to save changes in the filter.\n\n 5. Optional: If you want per-region alert for the regional metric,\n expand the **Across time series** header and select `location` in the\n **Time series group by** field.\n\n6. Click **Save policy**.\n\nUpdate Cloud Monitoring queries to use the regional quota metrics\n\nTo change the quota metric in an MQL-based alerting policy or a chart in\na dashboard, use the Query Editor and edit the query filter. See\n[Using the Query Editor](/monitoring/mql/query-editor).\n\nOpen the Query Editor and edit the filter for query metric as shown in the following\nexample:\n\nOptionally, you can group the alert based on a location by using the `group-by`\noperation:"]]
