Google Cloud has begun the automatic enablement of its new unified OpenTelemetry (OTel) ingestion API across all projects.
Starting March 4, 2026, the new endpoint telemetry.googleapis.com will be automatically activated for any Google Cloud project that has any of the existing observability ingestion APIs enabled (Cloud Logging, Cloud Monitoring, or Cloud Trace).
What This Means
- No action required from users.
- The new API supports logs, metrics, and traces in a single unified endpoint using the OpenTelemetry Protocol (OTLP).
- Existing services (Cloud Logging, Cloud Monitoring, Cloud Trace) continue to work without interruption.
- There is no downtime and no migration needed for most users.
This change is part of Google Cloud’s broader strategy to simplify observability by offering one native OpenTelemetry-native ingestion point instead of separate APIs for each signal type.
For new projects created via the Google Cloud Console or gcloud CLI, the new API is enabled by default when observability services are activated. For existing projects, Google is rolling out the automatic enablement progressively for those that already use the legacy ingestion endpoints.
The update was announced via official Google Cloud product update notifications in early February 2026.
This move makes it significantly easier for developers and platform teams to adopt OpenTelemetry standards on Google Cloud without changing their instrumentation pipelines.
