This page provides a brief overview of the Observability API and
the Telemetry (OTLP) API.

## About the Observability API

The Observability API lets you do the following:

- Configure default settings for observability buckets for projects, folders, and organizations. These
  settings help you meet your compliance and regulatory requirements. You can
  configure the following:

  - A default storage location for new observability buckets.
  - For each location, a default Cloud Key Management Service key. That key is used to encrypt new observability buckets.

  For more information, see
  [Set defaults for observability buckets](https://docs-0cloud-0google-0com.linkedin.net.nz/stackdriver/docs/observability/set-defaults-for-observability-buckets.md.txt).

  > [!NOTE]
  > **Note:** As of June 1, 2026, the create-observability bucket flow enforces organization policies that restrict locations, that require use of customer-managed encryption keys (CMEKs), and that restrict which Cloud Key Management Service keys can be used.

- Configure the observability scope for your project. This scope controls which
  resources are searched by the explorer pages for log, metric, and trace data.
  For more information, see [Configure observability scopes](https://docs-0cloud-0google-0com.linkedin.net.nz/stackdriver/docs/observability/scopes.md.txt).

- List information about the observability buckets in your Google Cloud project.
  Your trace data is stored in an observability bucket. For information about
  the data model, see [Storage overview](https://docs-0cloud-0google-0com.linkedin.net.nz/stackdriver/docs/observability/storage-overview.md.txt).

- Create a link on a dataset, which lets BigQuery have read access
  to the dataset. To learn how to create a linked dataset, see
  [Manage storage](https://docs-0cloud-0google-0com.linkedin.net.nz/stackdriver/docs/observability/storage-manage.md.txt).

### VPC Service Controls support

The Observability API service, whose service name is
`observability.googleapis.com`, is a VPC Service Controls-supported service.
For more information, see the following:

- [VPC Service Controls documentation](https://docs-0cloud-0google-0com.linkedin.net.nz/vpc-service-controls/docs.md.txt).
- [Details and limitations for the Observability API](https://docs-0cloud-0google-0com.linkedin.net.nz/vpc-service-controls/docs/supported-products.md.txt#table_observability_api).

### Service endpoints

A [service endpoint](https://google.aip.dev/9#api_service_endpoint) is a base URL that specifies the
network address of an API service. The Observability API supports a global
endpoint and regional endpoints:

- Global endpoint: `observability.googleapis.com`.

  You can use the global service endpoint to perform any operations supported
  by the Observability API. Additionally, for this endpoint, the list
  observability buckets command lets you replace the location field in the path
  parameter with the wildcard (`-`).
- Regional endpoints: `observability.REGION.rep.googleapis.com`, where
  <var translate="no">REGION</var> is a supported region. For a list of endpoints, see
  [Regional service endpoint](https://docs-0cloud-0google-0com.linkedin.net.nz/stackdriver/docs/reference/observability/api/rest.md.txt#regional-service-endpoint).

  You can use a regional service endpoint only when the location provided
  in the path parameter matches the endpoint's region. Commands sent to these
  service endpoints fail if they include a wildcard or if the location
  differs from the endpoint's region.

### API reference

- [REST reference](https://docs-0cloud-0google-0com.linkedin.net.nz/stackdriver/docs/reference/observability/api/rest.md.txt?rep_location=global).
- [gRPC reference](https://docs-0cloud-0google-0com.linkedin.net.nz/stackdriver/docs/reference/observability/api/rpc.md.txt).

## About the Telemetry API

The Telemetry (OTLP) API is an implementation of the
[OpenTelemetry OTLP Protocol](https://opentelemetry.io/docs/specs/otlp/#protocol-details). The Telemetry API
provides compatibility and support for the open source OpenTelemetry ecosystem:

- **Logs** : The Telemetry API lets you ingest OTLP-formatted log records
  to your project. For more information, see
  [OTLP ingestion overview](https://docs-0cloud-0google-0com.linkedin.net.nz/stackdriver/docs/otlp/overview.md.txt).

- **Metrics** : The Telemetry API lets you ingest OTLP-formatted metrics
  into Cloud Monitoring by using the `otlphttp` exporter and an
  OpenTelemetry Collector or an OpenTelemetry SDK. For more information, see
  [OTLP ingestion overview](https://docs-0cloud-0google-0com.linkedin.net.nz/stackdriver/docs/otlp/overview.md.txt).

- **Traces** : The Telemetry API lets you send OTLP-formatted trace data
  to your project. Also, the [trace limits](https://docs-0cloud-0google-0com.linkedin.net.nz/stackdriver/quotas.md.txt#telemetry-api-trace-limits) for the
  Telemetry API are often more generous than the limits for the
  Cloud Trace API.

### VPC Service Controls support

The Telemetry API service, whose service name is `telemetry.googleapis.com`,
is a VPC Service Controls-supported service. Any VPC Service Controls restrictions
that you create for the Telemetry API service apply
only to that service. Those restrictions don't apply to any
other services that can ingest log, metric, or trace data.
For more information about VPC Service Controls, see the following:

- [VPC Service Controls documentation](https://docs-0cloud-0google-0com.linkedin.net.nz/vpc-service-controls/docs.md.txt).
- [Details and limitations for the Telemetry API](https://docs-0cloud-0google-0com.linkedin.net.nz/vpc-service-controls/docs/supported-products.md.txt#table_telemetry).

### Service endpoints

A [service endpoint](https://google.aip.dev/9#api_service_endpoint)
is a base URL that specifies the
network address of an API service. The Telemetry API supports a global
endpoint and regional endpoints:

- Global endpoint: `telemetry.googleapis.com`. For this endpoint, after
  Google Cloud Observability successfully completes all validation steps, it sends the data
  to a backend service for storage.

- Regional endpoints: `telemetry.REGION.rep.googleapis.com`, where
  <var translate="no">REGION</var> is a supported region. For these endpoints, after Google Cloud Observability
  successfully completes all validation steps, it sends the data to a backend
  service. This service either stores or discards the data:

  - Log and trace data is stored. The backend service automatically moves data between regions when necessary.
  - Metric data is stored only when the location label attached to the data matches the endpoint's region or a zone within that region.

  For a list of supported regional endpoints, see the API reference pages.

The ingestion of trace data can trigger the creation of an observability bucket.
However, the use of a regional endpoint doesn't affect where the system creates
the observability bucket. The system determines the location of an
observability bucket using
[default settings](https://docs-0cloud-0google-0com.linkedin.net.nz/stackdriver/docs/observability/set-defaults-for-observability-buckets.md.txt),
organization policies, and the set of supported bucket locations.

### API reference

For more information about the Telemetry API, see the following documents:

- [Telemetry API overview](https://docs-0cloud-0google-0com.linkedin.net.nz/stackdriver/docs/reference/telemetry/overview.md.txt).
- [Telemetry API limits and quotas](https://docs-0cloud-0google-0com.linkedin.net.nz/stackdriver/quotas.md.txt#telemetry-api-limits).