# Export OTLP telemetry

Send runtime traces to an OTLP HTTP receiver with encrypted write-only headers.

Workspace owners can export runtime traces to an OpenTelemetry Protocol (OTLP) HTTP receiver.

## Configure the exporter

In the workspace:

1. Open **Settings**.
2. Open **Operations**.
3. Find the monitoring section.
4. Enter the OTLP traces endpoint.
5. Add the HTTP headers required by the destination.
6. Save the configuration.

Leaving the endpoint blank disables account-level telemetry export.

## Credentials

OTLP header values are:

* encrypted at rest;
* write-only after saving;
* scoped to the workspace configuration;
* excluded from run diagnostics and customer-visible logs.

Rotate a header by replacing its value and saving the configuration again.

## Content policy

Metadata-only telemetry is the recommended default.

The **Include prompt and response content** setting should remain disabled unless the destination is approved to receive customer content.

Lifecycle projections are bounded and sanitized. They can describe events such as:

* compaction;
* active-tool changes;
* resource changes;
* queue and cancellation transitions;
* session settlement.

They do not include prompt bodies, response bodies, tool arguments, tool results, skill contents or credentials.

## Verify the integration

1. Save the endpoint and headers.
2. Run a bounded test response.
3. Find the trace using the run or response identifier.
4. Confirm the expected run and session spans are present.
5. Confirm sensitive content is absent when content export is disabled.

## Troubleshooting

| Symptom                     | Check                                                              |
| --------------------------- | ------------------------------------------------------------------ |
| No traces                   | Endpoint, headers, workspace permissions and receiver availability |
| Authentication failure      | Rotate the destination header                                      |
| Missing content             | Content export is intentionally disabled by default                |
| Missing lifecycle event     | Confirm the run emitted the corresponding event                    |
| Duplicate or partial traces | Receiver retry and ingestion behavior                              |