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

# Export traces to Chronosphere

> Send Checkly traces to Chronosphere with a restricted service account token.

Before you start, read the prerequisites on the [OTLP export page](https://www.checklyhq.com/docs/integrations/observability/traces/otlp.md) and check [what is sent](https://www.checklyhq.com/docs/integrations/observability/traces/otlp.md#what-is-sent).
This page only covers the values Chronosphere needs.

Chronosphere is now Palo Alto Networks Cortex XCOR. The endpoint host is still `<instance>.chronosphere.io` and its documentation lives at docs-xcor.paloaltonetworks.com.

1. Get the endpoint. It is `https://<instance>.chronosphere.io/data/opentelemetry/v1/traces`.
2. Get the key. In Chronosphere, go to the admin view, then **Platform** > **Service Accounts**, and add a service account. Make it restricted and write-only. Copy the token right away, because Chronosphere shows it once.
3. Paste the values into Checkly. On the [Traces settings page](https://app.checklyhq.com/settings/account/traces), turn on **Enable exporting traces**, paste the URL, and add the header from the table below.
4. Find the spans. In Chronosphere, the spans appear under service `checkly`.

| Header name | Value |
| - | - |
| `API-Token` | `<service account token>` |

Chronosphere documents the endpoint in [OTLP endpoints](https://docs-xcor.paloaltonetworks.com/ingest/metrics-traces/otel/otlp-endpoints).

To see failed runs, filter on the attribute `checkly.check.status` with the value `FAILED`.
The [OTLP export page](https://www.checklyhq.com/docs/integrations/observability/traces/otlp.md) has the span schema.


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