> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chronosphere.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Use OpenTelemetry protocol endpoints

export const MyTenantList = () => <>
    <em><code>TENANT</code></em>: The name of your Observability Platform tenant.
  </>;

Chronosphere Observability Platform supports ingesting log data using OpenTelemetry
protocol (OTLP) HTTP ingestion endpoints.

<Note>
  For best results, ingest telemetry through a local OpenTelemetry Collector
  for processing and batching. Sending telemetry directly from an OpenTelemetry SDK
  can be less reliable.
</Note>

## Requirements

Your OTLP configuration must meet certain requirements.

* **`API-Token` header:** All requests must include the `API-Token` HTTP header,
  and its value must be the API token of a valid
  [service account](/administer/accounts-teams/service-accounts)
  with write permissions.
* **OTLP version support:** Only v1.0 and higher are supported.
* **Supported compression methods:** Chronosphere supports `gzip`, `snappy`,
  and `zstd` compression, and recommends `zstd`.
* **Encryption:** All requests must be encrypted using TLS.

### Recommendations

Chronosphere recommends setting the timeout value for a logs request to 30 seconds,
and to enable retries to prevent transient network errors from causing data loss.

## OTLP endpoint URLs

Observability Platform provides HTTP endpoints for logs, metrics, and traces.

| Telemetry type | HTTP endpoint URL                                              |
| -------------- | -------------------------------------------------------------- |
| Logs           | `https://TENANT.chronosphere.io/data/opentelemetry/v1/logs`    |
| Metrics        | `https://TENANT.chronosphere.io/data/opentelemetry/v1/metrics` |
| Traces         | `https://TENANT.chronosphere.io/data/opentelemetry/v1/traces`  |

<MyTenantList />

OpenTelemetry exporters complete the path based on the telemetry type. For the
`otlphttp` exporter, set the endpoint base path as follows:

```yaml theme={null}
exporters:
  otlphttp/chronosphere:
    endpoint: https://TENANT.chronosphere.io/data/opentelemetry/
    compression: zstd
    headers:
      API-Token: ${env:API_TOKEN}
    ...
```

For an example OTLP exporter configuration, see
[Configure the OpenTelemetry Collector](/ingest/metrics-traces/otel/otel-ingest#configure-the-opentelemetry-collector).