Stay organized with collections
Save and categorize content based on your preferences.
Cloud Quotas dimensions represent different ways of measuring resource
usage in Google Cloud. Dimensions are typically a region, zone, Google Cloud
user, or product attribute.
The Cloud Quotas API represents dimensions as key-value pairs. The key is
the dimension name (for example, region). The value is the assigned value
for the dimension (for example, a region such as us-central1).
For example, Compute Engine measures VM use by using different dimensions. The
region dimension measures the number of VMs you have in a given region.
Compute Engine also has a number of product attribute dimensions, including
gpu_family. The gpu_family dimension measures the number of GPUs of a
given family in your Google Cloud project.
View dimensions
You can view the dimensions for quotas and system limits by looking in the
Google Cloud console, using the Google Cloud CLI, querying the REST API, or through
client libraries. To view dimensions that you haven't specified a value for, use
the gcloud CLI. Also use the gcloud CLI to view dimensions
for quotas and system limits that don't have regional or zonal dimensions if
your project doesn't already use the associated resource. This section shows how
to view dimensions by using the console and by using the gcloud CLI.
Console
In the Google Cloud console, go to the
IAM & Admin > Quotas & System Limits page:
The table on this page displays dimensions in the Dimensions column.
If you don't see the Dimensions column, take the following steps.
Otherwise, skip this step.
Click view_columnColumn display options.
Select Dimensions.
Click OK. The Dimensions column appears in the table.
To filter the results, enter a property name or value in the field next to
filter_listFilter.
To filter by product, begin entering the product name and select from the
list that appears.
To filter by dimension, enter your dimension using the following format:
dimension_name:dimension_value. For example, to see quotas and system limits
defined for the us-central1 region, enter: region:us-central.
Understand blank dimensions
Sometimes the Dimensions column is empty. This can happen for the
following reasons:
The quota or system limit value is the default value and applies for all
dimensions. For some quotas and system limits, the console shows a line
that lists the default quota or system limit value for reference. Because
the default applies to all dimension values, the Dimensions column is
blank. Look at the Name column to identify these entries. The Name
column indicates these entries with the word "default" in parenthesis at
the end of the quota or system limit name.
For example, the quota SetIamPolicyRequestsPerMinutePerProject is defined
on the region dimension. The console shows a reference entry, and an
entry for each region. In the Name column, the reference entry is
listed as
"SetIAMPolicy requests per minute per region (default)." For this entry,
the Dimensions column is empty.
No dimensions apply. For example, the Compute Engine quota
NETWORKS-per-project isn't associated with a region, zone, or product
attribute, so there are no dimensions to display.
gcloud
You can use the gcloud CLI to view dimensions for a single quota or
system limit, or for all quotas and system limits associated with a given
product. Viewing dimensions for a single quota or system limit is usually
faster than viewing dimensions for all quotas and system limits associated
with a product. The response to a query for a single quota is typically about
200 lines. The response to a query for a product can exceed 2,000 lines.
View dimensions for a single quota or system limit with gcloud
To view dimensions for a single quota or system limit using the
gcloud CLI, run the following command in your terminal:
View all dimensions for the product associated with the quota or system
limit you're interested in. This command doesn't require the quota ID.
See the section
View dimensions for a product with gcloud CLI.
PROJECT_ID: The ID of your Google Cloud
project. To find your project ID, choose one of the following options:
If you set your current project as your default project in the
gcloud CLI configuration, find your project ID get by running the
following gcloud command in your terminal:
gcloudconfigget-valueproject
SERVICE_ID: the service ID of the product associated
with the quota or system limit. For example, if the quota is for Compute Engine
A2 CPUs, the service ID is compute.googleapis.com.
View dimensions for a product with gcloud CLI
To view dimensions for a single quota or system limit using the
gcloud CLI, run the following command in your terminal:
If you set your current project as your default project in the
gcloud CLI configuration, find your project ID get by running the
following gcloud command in your terminal:
gcloudconfigget-valueproject
SERVICE_ID: the service ID of the product associated
with the quota or system limit. For example, if the quota is for Compute Engine
A2 CPUs, the service ID is compute.googleapis.com.
Dimension precedence
Some use cases for the Cloud Quotas API have complex dimension setups.
Quotas can be configured at a more granular level than just regions and zones.
You can accomplish this granularity when you use service-specific dimensions.
For example, the gpu_family and network_id are service-specific dimensions
in the Compute Engine service. Dimensions are defined by each individual
service and each service might have a different set of service-specific
dimensions.
When working with either location dimensions or service-specific dimensions,
the following precedence is applied:
A quota preference configuration with all location and service-specific
dimensions specified takes precedence over any other configuration.
Configurations that specify location dimensions only take precedence over
configurations containing only service-specific dimensions.
Combining dimensions
In a quota preference configuration, you can combine dimensions in the following
ways:
The configuration may contain both location dimensions and service-specific
dimensions. This is the highest order in precedence.
The configuration may only contain location dimensions. This configuration
applies to all service-specific dimensions, except the ones explicitly
configured with method 1.
The configuration may only contain service-specific dimensions. This configuration
applies to all locations except those explicitly configured with method 1 or 2.
If the configuration contains any service-specific dimensions, it must contain
all service-specific dimensions.
You can have configurations without any dimensions. Such configurations
apply to all locations and all service-specific dimensions, except the ones
explicitly configured.
[[["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-25 UTC."],[[["\u003cp\u003eCloud Quotas dimensions, represented as key-value pairs, measure resource usage in Google Cloud, and these can be based on region, zone, user, or product attributes.\u003c/p\u003e\n"],["\u003cp\u003eDimensions for quotas and system limits can be viewed in the Google Cloud console or using the gcloud CLI, where the console displays them in the 'Dimensions' column, which can be filtered.\u003c/p\u003e\n"],["\u003cp\u003eAn empty 'Dimensions' column in the console indicates that the quota or system limit applies universally to all dimensions, or that no dimensions are associated with it, like the 'NETWORKS-per-project' quota.\u003c/p\u003e\n"],["\u003cp\u003eThe gcloud CLI allows for viewing dimensions for a single quota/system limit or for an entire product, where the single quota query is much faster than listing all the dimensions for a whole product.\u003c/p\u003e\n"],["\u003cp\u003eWhen configuring quotas, a setup with both location and service-specific dimensions takes the highest precedence, followed by configurations with only location dimensions, then those with only service-specific dimensions.\u003c/p\u003e\n"]]],[],null,["# Configure Cloud Quotas dimensions\n\nCloud Quotas dimensions represent different ways of measuring resource usage in Google Cloud. Dimensions are typically a region, zone, Google Cloud user, or product attribute.\n\n\u003cbr /\u003e\n\nThe Cloud Quotas API represents dimensions as key-value pairs. The `key` is\nthe dimension name (for example, `region`). The `value` is the assigned value\nfor the dimension (for example, a region such as `us-central1`).\n\nFor example, Compute Engine measures VM use by using different dimensions. The\n`region` dimension measures the number of VMs you have in a given region.\nCompute Engine also has a number of product attribute dimensions, including\n`gpu_family`. The `gpu_family` dimension measures the number of GPUs of a\ngiven family in your Google Cloud project.\n\nView dimensions\n---------------\n\nYou can view the dimensions for quotas and system limits by looking in the\nGoogle Cloud console, using the Google Cloud CLI, querying the REST API, or through\nclient libraries. To view dimensions that you haven't specified a value for, use\nthe gcloud CLI. Also use the gcloud CLI to view dimensions\nfor quotas and system limits that don't have regional or zonal dimensions if\nyour project doesn't already use the associated resource. This section shows how\nto view dimensions by using the console and by using the gcloud CLI. \n\n### Console\n\n1. In the Google Cloud console, go to the\n **IAM \\& Admin \\\u003e Quotas \\& System Limits** page:\n\n\n [Go to Quotas \\& System Limits](https://console.cloud.google.com/iam-admin/quotas)\n\n \u003cbr /\u003e\n\n The table on this page displays dimensions in the **Dimensions** column.\n2. If you don't see the **Dimensions** column, take the following steps.\n Otherwise, skip this step.\n\n 1. Click view_column **Column display options**.\n 2. Select **Dimensions**.\n 3. Click **OK** . The **Dimensions** column appears in the table.\n3. To filter the results, enter a property name or value in the field next to\n filter_list **Filter**.\n\n - To filter by product, begin entering the product name and select from the list that appears.\n - To filter by dimension, enter your dimension using the following format: `dimension_name:dimension_value`. For example, to see quotas and system limits defined for the us-central1 region, enter: `region:us-central`.\n\n### Understand blank dimensions\n\nSometimes the **Dimensions** column is empty. This can happen for the\nfollowing reasons:\n\n- The quota or system limit value is the default value and applies for all\n dimensions. For some quotas and system limits, the console shows a line\n that lists the default quota or system limit value for reference. Because\n the default applies to all dimension values, the **Dimensions** column is\n blank. Look at the **Name** column to identify these entries. The **Name**\n column indicates these entries with the word \"default\" in parenthesis at\n the end of the quota or system limit name.\n\n For example, the quota `SetIamPolicyRequestsPerMinutePerProject` is defined\n on the `region` dimension. The console shows a reference entry, and an\n entry for each region. In the **Name** column, the reference entry is\n listed as\n \"SetIAMPolicy requests per minute per region (default).\" For this entry,\n the **Dimensions** column is empty.\n- No dimensions apply. For example, the Compute Engine quota\n `NETWORKS-per-project` isn't associated with a region, zone, or product\n attribute, so there are no dimensions to display.\n\n### gcloud\n\n\n| **Preview\n| --- gcloud CLI for Cloud Quotas**\n|\n|\n| This feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\n\u003cbr /\u003e\n\nYou can use the gcloud CLI to view dimensions for a single quota or\nsystem limit, or for all quotas and system limits associated with a given\nproduct. Viewing dimensions for a single quota or system limit is usually\nfaster than viewing dimensions for all quotas and system limits associated\nwith a product. The response to a query for a single quota is typically about\n200 lines. The response to a query for a product can exceed 2,000 lines.\n\n### View dimensions for a single quota or system limit with gcloud\n\nTo view dimensions for a single quota or system limit using the\ngcloud CLI, run the following command in your terminal: \n\n```bash\ngcloud beta quotas info describe QUOTA_ID --project=PROJECT_ID --service=SERVICE_ID\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eQUOTA_ID\u003c/var\u003e: the ID for the quota or system limit. If\n you don't know your quota ID, choose one of the following options:\n\n 1. Find it by using the console as described in [Find your quota ID](/docs/quotas/gcloud-cli-examples#find_your_quota_id).\n 2. View all dimensions for the product associated with the quota or system limit you're interested in. This command doesn't require the quota ID. See the section [View dimensions for a product with gcloud CLI](#gcloud-view-product).\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: The ID of your Google Cloud\n project. To find your project ID, choose one of the following options:\n\n 1. To find your project ID by using the console, see [Identifying projects](/resource-manager/docs/creating-managing-projects#identifying_projects).\n 2. If you set your current project as your default project in the gcloud CLI configuration, find your project ID get by running the following gcloud command in your terminal: \n\n ```bash\n gcloud config get-value project\n ```\n- \u003cvar translate=\"no\"\u003eSERVICE_ID\u003c/var\u003e: the service ID of the product associated\n with the quota or system limit. For example, if the quota is for Compute Engine\n A2 CPUs, the service ID is `compute.googleapis.com`.\n\n### View dimensions for a product with gcloud CLI\n\nTo view dimensions for a single quota or system limit using the\ngcloud CLI, run the following command in your terminal: \n\n```bash\ngcloud beta quotas info list --project=PROJECT_ID --service=SERVICE_ID\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: The ID of your Google Cloud\n project. To find your project ID, choose one of the following options:\n\n 1. To find your project ID by using the console, see [Identifying projects](/resource-manager/docs/creating-managing-projects#identifying_projects).\n 2. If you set your current project as your default project in the gcloud CLI configuration, find your project ID get by running the following gcloud command in your terminal: \n\n ```bash\n gcloud config get-value project\n ```\n- \u003cvar translate=\"no\"\u003eSERVICE_ID\u003c/var\u003e: the service ID of the product associated\n with the quota or system limit. For example, if the quota is for Compute Engine\n A2 CPUs, the service ID is `compute.googleapis.com`.\n\nDimension precedence\n--------------------\n\nSome use cases for the Cloud Quotas API have complex dimension setups.\nQuotas can be configured at a more granular level than just regions and zones.\nYou can accomplish this granularity when you use service-specific dimensions.\nFor example, the `gpu_family` and `network_id` are service-specific dimensions\nin the Compute Engine service. Dimensions are defined by each individual\nservice and each service might have a different set of service-specific\ndimensions.\n\nWhen working with either location dimensions or service-specific dimensions,\nthe following precedence is applied:\n\n1. A quota preference configuration with all location and service-specific\n dimensions specified takes precedence over any other configuration.\n\n2. Configurations that specify location dimensions only take precedence over\n configurations containing only service-specific dimensions.\n\nCombining dimensions\n--------------------\n\nIn a quota preference configuration, you can combine dimensions in the following\nways:\n\n1. The configuration may contain *both* location dimensions and service-specific\n dimensions. This is the highest order in precedence.\n\n2. The configuration may *only* contain location dimensions. This configuration\n applies to all service-specific dimensions, except the ones explicitly\n configured with method 1.\n\n3. The configuration may *only* contain service-specific dimensions. This configuration\n applies to all locations except those explicitly configured with method 1 or 2.\n\n4. If the configuration contains *any* service-specific dimensions, it must contain\n all service-specific dimensions.\n\n5. You can have configurations *without any* dimensions. Such configurations\n apply to all locations and all service-specific dimensions, except the ones\n explicitly configured."]]
