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

# Use OpenTelemetry protocol endpoints

> Learn how to configure and use Palo Alto Networks Cortex XCOR endpoints for OpenTelemetry protocol ingestion of log data.

Palo Alto Networks Cortex XCOR 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.

## 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](https://docs-xcor.paloaltonetworks.com/administer/accounts-teams/service-accounts.md)
  with write permissions.
* **OTLP version support:** Only v1.0 and higher are supported.
* **Supported compression methods:** Cortex XCOR supports `gzip`, `snappy`,
  and `zstd` compression, and recommends `zstd`.
* **Encryption:** All requests must be encrypted using TLS.

### Recommendations

Cortex XCOR 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

Cortex XCOR 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` |

*`TENANT`*: The name of your Cortex XCOR tenant.

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](https://docs-xcor.paloaltonetworks.com/ingest/metrics-traces/otel/otel-ingest.md#configure-the-opentelemetry-collector).


## Related topics

- [Use OpenTelemetry protocol endpoints](https://docs-xcor.paloaltonetworks.com/ingest/metrics-traces/otel/otlp-endpoints.md)
- [Ingest DogStatsD metrics with the OpenTelemetry Collector](https://docs-xcor.paloaltonetworks.com/ingest/metrics-traces/otel/ingest-dogstatsd.md)
- [OpenTelemetry support in Cortex XCOR](https://docs-xcor.paloaltonetworks.com/ingest/otel-ingestion.md)
- [Configure ingestion and processing of OpenTelemetry Metrics](https://docs-xcor.paloaltonetworks.com/ingest/metrics-traces/otel/otel-config.md)
- [Integrate with Cortex XCOR](https://docs-xcor.paloaltonetworks.com/integrate.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.