OpenTelemetry export
Cloudflare exports telemetry to destinations that support the OpenTelemetry Protocol (OTLP). Use these destinations with Cloudflare telemetry and your existing observability tools.
Supported telemetry
You can export these telemetry types:
- Cloudflare Traces - Traces showing production request paths through Cloudflare
- Workers Traces - Traces showing requests through Workers and connected services
- Workers Logs - Application and system logs, including
console.log()output
Available destinations
These endpoint formats cover common observability providers. Check your provider documentation for current authentication requirements.
| Provider | Traces endpoint | Logs endpoint |
|---|---|---|
| Honeycomb | https://api.honeycomb.io/v1/traces |
https://api.honeycomb.io/v1/logs |
| Grafana Cloud | https://otlp-gateway-<REGION>.grafana.net/otlp/v1/traces |
https://otlp-gateway-<REGION>.grafana.net/otlp/v1/logs |
| Firetiger | https://ingest.cloud.firetiger.com/v1/traces |
https://ingest.cloud.firetiger.com/v1/logs |
| Axiom | https://api.axiom.co/v1/traces |
https://api.axiom.co/v1/logs |
| Sentry | https://<HOST>/api/<PROJECT_ID>/integration/otlp/v1/traces |
https://<HOST>/api/<PROJECT_ID>/integration/otlp/v1/logs |
| Sematext | https://otlp-receiver.sematext.com (US), https://otlp-receiver.eu.sematext.com (EU) |
https://otlp-receiver.sematext.com (US), https://otlp-receiver.eu.sematext.com (EU) |
| PostHog | Not supported | https://<REGION>.i.posthog.com/i/v1/logs |
| Datadog | https://cloudflare.integrations.otlp.<DD_SITE>/v1/traces |
https://cloudflare.integrations.otlp.<DD_SITE>/v1/logs |
| New Relic | https://otlp.nr-data.net/v1/traces |
https://otlp.nr-data.net/v1/logs |
| Splunk Observability | https://ingest.<REALM>.signalfx.com/v2/trace/otlp |
N/A |
| Splunk Platform | http://splunk.internal:4318/v1/traces |
http://splunk.internal:4318/v1/logs |
| SigNoz | https://ingest.<region>.signoz.cloud:443/v1/traces |
https://ingest.<region>.signoz.cloud:443/v1/logs |
:::note[Authentication] Most providers require authentication headers. Check your provider documentation for specific requirements. :::
Create a destination
Create an account-level Cloudflare Observability destination first.
:::note[Protocol] Cloudflare does not support the binary format for OTLP ingestion. :::

-
In the Cloudflare dashboard, go to Observability > Destinations.
-
Select Add destination.
-
Configure the destination:
- Destination name - Enter a descriptive name, such as
grafana-traces. - Destination type - Select Traces or Logs.
- OTLP endpoint - Enter the provider endpoint for your telemetry type.
- Custom headers - Add any provider authentication headers.
- Destination name - Enter a descriptive name, such as
-
Select Save.

Enable export for Cloudflare Traces
Add the destination under Export destinations in your domain settings. Refer to Cloudflare Traces configuration.
Enable OpenTelemetry export for your Worker
Configure and redeploy your Worker after creating a destination. Refer to Workers OpenTelemetry export.
Check destination status
The dashboard shows each destination delivery status. The status reflects the most recent delivery attempt.
| Status | Description | Troubleshooting |
|---|---|---|
| Last: n minutes ago | Cloudflare delivered data recently. | No action required |
| Never run | Cloudflare has not delivered data. | Check source traffic, export settings, and sampling rates |
| Error | Cloudflare could not deliver data. | Check the OTLP endpoint and authentication headers |
Known limitations
Some providers do not support every OTLP telemetry type. Check the available destinations and your provider documentation.
谢谢你的反馈!