Cloud Monitoring quotas and limits

This document lists the quotas and system limits that apply to Cloud Monitoring.

  • Quotas have default values, but you can typically request adjustments.
  • System limits are fixed values that can't be changed.

Google Cloud uses quotas to help ensure fairness and reduce spikes in resource use and availability. A quota restricts how much of a Google Cloud resource your Google Cloud project can use. Quotas apply to a range of resource types, including hardware, software, and network components. For example, quotas can restrict the number of API calls to a service, the number of load balancers used concurrently by your project, or the number of projects that you can create. Quotas protect the community of Google Cloud users by preventing the overloading of services. Quotas also help you to manage your own Google Cloud resources.

The Cloud Quotas system does the following:

In most cases, when you attempt to consume more of a resource than its quota allows, the system blocks access to the resource, and the task that you're trying to perform fails.

Quotas generally apply at the Google Cloud project level. Your use of a resource in one project doesn't affect your available quota in another project. Within a Google Cloud project, quotas are shared across all applications and IP addresses.

For more information, see the Cloud Quotas overview.

To adjust most quotas, use the Google Cloud console. For more information, see Request a quota adjustment.

There are also system limits on Monitoring resources. System limits can't be changed.

Monitoring API quotas and limits

Category Maximum value
Limits to API usage

To find the API quotas and limits, do one of the following:

Lifetime of API page tokens 24 hours
Maximum response size

200 MB

Applies to the size of the serialized response payload, which includes both the raw data and the label keys and values for every time series returned. If a query's response exceeds 200 MB, then the request fails with a RESOURCE_EXHAUSTED (HTTP 429 Too Many Requests) error.

To prevent or resolve RESOURCE_EXHAUSTED errors, do the following:

  • Reduce the cardinality of your metrics or apply filters to reduce the number of time series.
  • Increase the alignment period.
  • Decrease the time range of the query.
  • If you are using PromQL, then consider implementing Recording Rules.

Data retention

Metric data points older than the retention period are deleted from time series.

Category Value
Retention of data points for some Google Cloud services, including most metrics within the following categories:
  • Compute Engine metrics, prefix compute.googleapis.com
  • GKE metrics, prefix kubernetes.io
  • Cloud Storage metrics, prefix storage.googleapis.com
  • BigQuery metrics, prefix bigquery.googleapis.com
24 months1
Retention of all other Google Cloud metrics 6 weeks
Lifetime of API page tokens 24 hours