Quotas and limits

This page provides details on the limits that apply to using Cloud Logging.

Logging usage limits

The following limits apply to the usage of Cloud Logging. With the exception of the limits on the number of log buckets and sinks, these limits are fixed; you can't increase or decrease them.

¹ This approximate limit is based on internal data sizes, not the actual REST API request size.
² Cloud Logging truncates oversized label keys and values when their associated log entry is written.
³ This limit also applies to billing accounts, folders, and organizations and isn't hierarchical. For example, if you have multiple Trusted Cloud projects in an organization, then you could configure up to 200 sinks for each Trusted Cloud project; for that same organization, you could also configure up to 200 sinks at the organization level.
⁴ This limit is the maximum number of buckets that might contain log entries for a resource. For more information, see Query returns an error.
⁵ This limit includes buckets that are pending deletion.
⁶ Log entries with timestamps outside of these boundaries are rejected from log buckets. The Logging API accepts entries with older timestamps, and those entries can be routed to sink destinations but not stored in log storage. The Logging API rejects entries with timestamps more than 1 day in the future and returns an INVALID_ARGUMENT error.
⁷This feature is in Public Preview.

Logging API quotas and limits

The following limits apply to your usage of the Logging API. You can request changes to your Logging API quotas and limits; for instructions, see Requesting changes to Cloud Logging API quota on this page.

¹ Using exclusion filters doesn't reduce this number because logs are excluded after the entries.write request is made.
²This value is the default setting.
³ This limit also applies to billing accounts, folders, and organizations and isn't hierarchical.
⁴ The logName field of a log entry specifies the log entry's resource name.
⁵ The daily control-request quota applies to API requests for creating and updating exclusions and sinks. The per-minute control-request quota applies to everything also included in the daily control-request quota, plus API requests for deleting logs and managing log-based metrics.
⁶ If the rate of exports exceeds the quota, then the error is recorded in a log entry. The summary field indicates sink configuration error and the error code is listed as topic_over_quota.

Per-region ingestion quotas

Starting on August 4, 2025, Cloud Logging quotas will limit, on a per-Trusted Cloud project basis, the volume of data written to an ingestion region. On August 4, 2025, Cloud Logging will stop limiting the number of API entries.write requests from a Trusted Cloud project. This change is intended to improve isolation and protect regional resources from ingestion overload.

The following table shows the default quota for each region:

The default values for the regional quotas exceed the ingestion volumes of most users. However, if before August 4, 2025, your project's ingestion volume from a region in the previous six or more months is close to or above the default quota for that region, then your initial quota includes an automatic, one-time increase. Therefore, your quotas might be higher than the defaults in the preceding table.

You can review your regional quotas before August 4, 2025, but the quotas aren't enforced until after that date. For information about reviewing quotas, see Review your Logging quotas.

On August 4, 2025, the quota for the number of entries.write requests will be changed to unlimited.

On August 11, 2025, the quota for the number of entries.write requests will be removed.

If you exceed a regional quota after August 4, 2025, your write requests to the Cloud Logging API might be rejected with a "resource exhausted" error message. For recommendations to help you avoid exceeding quotas, see Manage and monitor your Logging quotas.

Review your Cloud Logging API quotas

To review your Cloud Logging API quotas, do the following:

1. In the Trusted Cloud console, go to the Quotas & System Limits page:

   Go to Quotas & System Limits

   If you use the search bar to find this page, then select the result whose subheading is IAM & Admin.

2. Filter the list of quotas for the Cloud Logging API service.

Request changes to Cloud Logging API quota

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

Manage and monitor your Cloud Logging API quotas

To prevent service disruptions caused by exceeding quotas, you can do the following:

• Use automatic quota adjustment to monitor your quota usage and request increases for you. For more information, see Quota adjuster.
• Create alerts on quotas to notify you about usage. For more information, see Set up quota alerts.

Optimize usage of entries.list

The expected usage of entries.list is to search for matching logs. This method isn't intended for high-volume retrieval of log entries. If you're regularly exhausting your entries.list quota, then consider the following options:

• Ensure that you are using the Cloud Logging API effectively. For more information, see Optimize usage of the API.

• If you know in advance that the log entries you want to analyze exceed the entries.list quota, then configure a log sink to export your logs to a supported destination.

Audit logging

The maximum sizes of audit logs are shown in the following table. These values can help you estimate the space you need in your sink destinations.

Logs retention periods

The following Cloud Logging retention periods apply to log buckets, regardless of which types of logs are included in the bucket or whether they were copied from another location. The retention information is as follows: