Mike's Notes
Changes on Google Cloud
Resources
- https://opentelemetry.io/docs/specs/otlp/
- https://opentelemetry.io/docs/languages/
- https://docs.cloud.google.com/stackdriver/docs/reference/telemetry/overview
- https://docs.cloud.google.com/stackdriver/docs/reference/telemetry/api
- https://docs.cloud.google.com/stackdriver/quotas#telemetry-api-limits
- https://docs.cloud.google.com/stackdriver/docs/reference/telemetry/trace-schema
References
- OTLP Specification 1.9.0
Repository
- Home > Ajabbi Research > Library >
- Home > Handbook >
Last Updated
15/02/2026
Automatic enablement of new OpenTelemetry ingestion API
By:
Google Cloud: 13/02/2026
.
We’re writing to let you know that Cloud Observability has launched a new OpenTelemetry (OTel) ingestion API that supports native OpenTelemetry Protocol (OTLP) logs, trace spans, and metrics.
Starting March 23, 2026, this API will be added as a dependency for the current Cloud Logging, Cloud Trace, and Cloud Monitoring ingestion APIs. This change ensures a seamless transition as collection tools migrate to this new unified endpoint.
What you need to know
Key changes:
- The existing Cloud Observability ingestion APIs (logging.googleapis.com, cloudtrace.googleapis.com, and monitoring.googleapis.com) are automatically activated when you create a Google Cloud project using the Google Cloud console or gcloud CLI. The behavior remains unchanged for projects created via API, which do not have these ingestion APIs enabled by default. Starting March 23, 2026, the new OTel ingestion endpoint telemetry.googleapis.com will automatically activate when any of these specified APIs are enabled.
- In addition, we will automatically enable this new endpoint for all existing projects that already have current ingestion APIs active.
What you need to do
No action is required from you for this API enablement change, and there will be no disruption to your existing services. You may disable the API at any time by following these instructions.
No comments:
Post a Comment