This document describes the quota metrics for regional APIs and the limitfor each metric. It also describes how to update your Cloud Monitoringdashboards, alerting policies and queries to use the regional metrics.

Regional API quota metrics

Compute Engine regional APIs that used the global quota metrics aremigrated to use the regional metrics. Global APIs continue to use the globalmetrics and quota limits. SeeAPI rate limits for global metrics.

For more information about the methods that use the regional metrics and thelimits, seeAPI rate limits for regional metrics.

The following table lists all metrics that are migrated from the global API quotametrics to regional metrics:

The following metrics don't have any global APIs. If you are referencing thesemetrics in the Cloud Monitoring dashboards, alerts, or queries, youmustmigrate these metrics to the corresponding regional metrics.

The following metrics don't have any regional or zonal APIs. Therefore, nochanges are required for regional API quota migration.

• compute.googleapis.com/project_set_common_instance_metadata_requests
• compute.googleapis.com/license_insert_requests

Migrate Cloud Monitoring metrics

When you migrate from the existing API quota metrics to the regional API quotametrics, you must manually update the Cloud Monitoring dashboards, alerts, andqueries to use regional metrics.

Update Cloud Monitoring dashboard to use the regional metrics

To update a Cloud Monitoring dashboard that monitors a global API quotametric to a regional metric, do the following:

1. In the Google Cloud console, selectMonitoring.
2. In the navigation pane, selectDashboards.
3. Select the dashboard that you want to edit to use a regional metric.
4. ClickEdit dashboard.

5. Edit the filter that corresponds to the metric that you want to migrate:

   1. In theFilter field, selectquota_metric.
   2. In theComparator field, select=~.

   3. In theValue field, specify the metric name for the regional API quota.For example, the filterquota_metric =~ compute.googleapis.com/read_requests.*uses a regular expression to match all time-series data that uses the quotametriccompute.googleapis.com/read_requests.*.

      

      For more information about the metrics, seeAPI rate limits for regional metrics.

   4. ClickDone to save changes.

   5. Optional: If you want to view the usage of quota per region,expand theGrouped header and selectlocation in theGroup by field.

6. ClickClose 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 aregional metric, do the following:

1. In the Google Cloud console, selectMonitoring.
2. In the navigation pane, selectAlerting.The Alerting page displays panes that list summary information, incidents,and alerting policies.
3. Click the alerting policy that you want to edit to use a regional metric.
4. ClickEdit to modify the policy.

5. Edit the filter that corresponds to the metric that you want to migrate:

   1. In theFilter field, selectquota_metric.
   2. In theComparator field, select=~.

   3. In theValue field, specify the metric name for the regional API quota.For example, the filterquota_metric =~ compute.googleapis.com/read_requests.*uses a regular expression to match all time-series data that uses the quotametriccompute.googleapis.com/read_requests.*.

      

      For more information about the metrics, seeAPI rate limits for regional metrics.

   4. ClickDone to save changes in the filter.

   5. Optional: If you want a per-region alert for the regional metric,expand theAcross time series header and selectlocation in theTime series group by field.

6. ClickSave policy.

Update Cloud Monitoring queries to use the regional quota metrics

To change the quota metric in a PromQL-based alerting policy or a chart ina dashboard, use the code editor and edit the query filter. SeeUsing the code editor for PromQL.

Open the code editor and edit the query as shown in the following example:

rate({   "__name__"="serviceruntime.googleapis.com/quota/rate/net_usage",   "monitored_resource"="consumer_quota",   "quota_metric"=~"compute.googleapis.com/read_requests.*"}[${__interval}])

Optionally, you can group the results based on a location by using thesum by operation:

sum by (location) (   rate({       "__name__"="serviceruntime.googleapis.com/quota/rate/net_usage",       "monitored_resource"="consumer_quota",       "quota_metric"=~"compute.googleapis.com/read_requests.*"   }[${__interval}]))