We’re enabling a new OTLP ingestion API starting Jun 1, 2026.
|
|
| Hello 布甲, You may have previously received a notification regarding this update. If so, please disregard this message. 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 June 1, 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 knowKey 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 June 1, 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 doNo 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. Refer to the attachment for a list of the projects that will automatically enable the new endpoint. We’re here to helpIf you have any questions or require assistance, please contact Google Cloud Support. Thanks for choosing Google Cloud Observability. |
|
|
|
|
|
|
|
|
|
project_number,project_id,project_name
56781264524,ordinal-brace-488708-q4,My Project 60788
