Google Cloud has made it easier for users to utilize the OpenTelemetry Protocol (OTLP) as a natively traced protocol in their Cloud Trace service. By adopting OTLP as a default protocol, Google Cloud is visibly opting for an open source monitoring strategy, indicating that cloud providers are no longer inclined towards the traditional vendor specific solutions. Consequently, they can now send trace data directly to the telemetry.googleapis.com endpoint, which simplifies client-side operations and removes the need for custom exporters.
OpenTelemetry, an industry standard for telemetry data exchange, is a vendor neutral solution that allows companies to gather and move metrics, logs, and traces from different platforms. Google Cloud by implementing the protocol at the storage layer has thus extended its compatibility beyond just being able to work with other protocols. Its redesigned system now uses the OpenTelemetry data model natively, lifting many of the technical limits that previously constrained developers.
For example, attribute keys can now extend up to 512 bytes, while attribute values support up to 64 kilobytes. Span names have increased to 1,024 bytes, and spans themselves can hold 1,024 attributes, 256 events, and 128 links. These changes give teams more flexibility in how they design and monitor distributed applications.
Product managers Sujay Solomon and Keith Chen described the update as the first step in a larger OpenTelemetry adoption strategy. Google’s approach, they said, focuses on simplifying telemetry ingestion at scale, with future plans to expand into managed processing and routing features.
The new OTLP endpoint also aligns Cloud Trace more closely with community standards. The Trace Explorer interface now incorporates OpenTelemetry semantic conventions, which may help developers already familiar with the ecosystem adapt more quickly.
Industry analysts point out that Google Cloud’s move contrasts with strategies taken by AWS and Microsoft Azure. While AWS relies on its ADOT distribution and hybrid integration, Azure has centered its approach on SDKs and application-level tooling. The decision by Google to redesign its internal storage system signals a focus that is more pronounced on infrastructure that is native to the protocol.
The firm is motivating present users of Cloud Trace to move to the OTLP endpoint, notably those with large data volumes.To facilitate the change, Google has published migration instructions and expects the protocol to become the standard method of ingestion across all Google Cloud Observability services.
