Quotas and limits

This document provides quota and limit information for Google Cloud Observability. For service-specific quota and limit information, see the following documents:

Telemetry API limits

This section describes only the quotas and limits that apply to the Telemetry (OTLP) API for ingestion of trace and metric data:

These quotas and limits apply only to the data being ingested by using the Telemetry API. After data is ingested, the following quotas and limits apply:

Limits for ingestion of traces

This section lists the limits that apply when the Telemetry API is used to ingest trace data. This API is designed for use with applications that are instrumented by using one of the OpenTelemetry SDKs.

Description Value Note
Maximum size of attribute keys 512 bytes Limit.
Maximum size of attribute values 64 KiB Limit.
Maximum size of a Span* object's name 1024 bytes Limit.
Maximum number of attributes attached to a Span* object 1024 Limit.
Maximum number of resource attributes per ResourceSpans* object 1024 Limit.
Maximum number of attributes per ResourceSpan* object
Includes attributes attached to child objects of the following types:
Resource, Span, ScopeSpans, Event, and Link.		 8192 Limit.
Maximum number of Event* objects per Span* object 256 Limit.
Maximum number of Link* objects per Span* object 128 Limit.
Maximum size of an Event* object's name 1024 bytes Limit.
Maximum number of attributes per Event* object 1024 Limit.
Maximum attributes per Link* object 1024 Limit.
Maximum size of schema URLs 8192 bytes Limit.
Maximum number of trace-ingestion bytes per minute

2.4 GB for the following regions: asia-east1, asia-northeast1, asia-southeast1, asia-south1, europe-west1, europe-west2, europe-west3, europe-west4, us-central1, us-east4, us-west1.

300 MB for all other regions.

 Quota.
*  For a definition of this structure, see the trace.proto file.

The Cloud Trace quotas and limits also apply when using the Telemetry API for trace ingestion.

Limits and quotas for ingestion of metrics

This section lists the limits and quotas that apply when the Telemetry API is used to ingest metric data.

Description Value Note
Maximum number of datapoints per request 200 Limit
Maximum number of ResourceMetrics per request 200 Limit
Maximum number of quantiles per Summary metric 10 Limit
Number of metric-ingestion requests per minute per region (quota) 60,000 Quota

The Cloud Monitoring quotas and limits also apply when using the Telemetry API for metric ingestion.

Limits and quotas for ingestion of logs

This section describes the limits and quotas that apply when the Telemetry API ingests log data.

Description Value Notes
Maximum number of logs per OTLP request 8192 Refers to the maximum number of logRecords in an OTLP resourceLogs structure. Limit.
Maximum size of each request 5 MiB Limit.
Maximum size of a LogEntry
that is created from an OTLP log record		 256 KiB Cloud Logging truncates or discards data from an OTLP log record when necessary. Limit.
Maximum length of an attribute key 512 B Oversized label keys are truncated when the OTLP log record is converted into a LogEntry. Limit.
Maximum length of an attribute value 64 KiB Oversized label values when the OTLP log record is converted into a LogEntry. Limit.
Maximum depth of attribute nesting 5 Attributes that exceed this limit are truncated when the OTLP log record is converted into a LogEntry.
Maximum number of log-ingestion bytes per minute

2.4 GB for the following regions: asia-east1, asia-northeast1, asia-southeast1, asia-south1, europe-west1, europe-west2, europe-west3, europe-west4, us-central1, us-east4, us-west1.

300 MB for all other regions.

 Quota.

The Cloud Logging quotas and limits also apply when the Telemetry API ingests log data.

View and manage your quotas

To learn more about quotas, including how to view and manage quotas, see the Cloud Quotas documentation.

To view your current quota usage, in the Google Cloud console, go to APIs & Services or click the following button:

Go to APIs & Services