Quotas and limits

This document lists the quotas and limits that apply to Error Reporting.

A quota restricts how much of a shared Google Cloud resource your Google Cloud project can use, including hardware, software, and network components. Therefore, quotas are a part of a system that does the following:

  • Monitors your use or consumption of Google Cloud products and services.
  • Restricts your consumption of those resources, for reasons that include ensuring fairness and reducing spikes in usage.
  • Maintains configurations that automatically enforce prescribed restrictions.
  • Provides a means to request or make changes to the quota.

In most cases, when a quota is exceeded, the system immediately blocks access to the relevant Google resource, and the task that you're trying to perform fails. In most cases, quotas apply to each Google Cloud project and are shared across all applications and IP addresses that use that Google Cloud project.

To increase or decrease most quotas, use the Google Cloud console. For more information, see Request a higher quota.

There are also limits on Error Reporting resources. These limits are unrelated to the quota system. Limits cannot be changed unless otherwise stated.

API activity limits

Quota name Limit
Error event data requests per minute per user 60
Error group metadata requests per minute per user 60
Error reports per minute 6,000

You can also see the API dashboard for your current API activity and quotas. Click on an API and select Quotas to see your limits.

Request changes to Error Reporting API quota

You can request higher or lower Error Reporting API limits using the Google Cloud console. For more information, see View and manage quotas.

If you get an error Edit is not allowed for this quota, you can contact Support to request changes to the quota. Note also that billing must be enabled on the Google Cloud project to click the checkboxes.

Deployment limits

There is a limit of 10,000 deployment-error group pairs, where a deployment is a combination of service and version. Once you have reached this limit, Error Reporting will discard the oldest (or less-recently modified) deployments and their associated error data.

Data retention periods

Information in Error Reporting is retained for 30 days.