Sentry provides distributed tracing, logs, and application monitoring. Export Cloudflare telemetry to query data and create alerts or dashboards.
This guide configures Sentry to receive Cloudflare traces and logs.
Before you begin, you need an active Sentry account ↗︎. You also need Cloudflare logs or traces to export.
Skip this step if you already have a project.
- Log in to your Sentry account ↗︎.
- Go to Insights > Projects.
- Select New Project ↗︎.
- Complete the project form, then select Create Project.
Sentry provides separate OpenTelemetry Protocol (OTLP) endpoints for traces and logs:
- Traces:
https://<HOST>/api/<PROJECT_ID>/integration/otlp/v1/traces - Logs:
https://<HOST>/api/<PROJECT_ID>/integration/otlp/v1/logs
- In Sentry, go to Settings > Projects ↗︎.
- Select your project.
- Under SDK Setup, select Client Keys (DSN).
- Copy the OTLP endpoints and authentication header.
For endpoint details, refer to Sentry OTLP documentation ↗︎.
In the Cloudflare dashboard, go to Observability > Destinations.
Go to OpenTelemetry ↗- Select Add destination.
- Configure the destination:
- Destination name:
sentry-traces - Destination type: Traces
- OTLP endpoint: Your Sentry OTLP traces endpoint
- Custom header name:
x-sentry-auth - Custom header value:
sentry sentry_key=<SENTRY_PUBLIC_KEY>
- Destination name:
- Select Save.
- Select Add destination.
- Configure the destination:
- Destination name:
sentry-logs - Destination type: Logs
- OTLP endpoint: Your Sentry OTLP logs endpoint
- Custom header name:
x-sentry-auth - Custom header value:
sentry sentry_key=<SENTRY_PUBLIC_KEY>
- Destination name:
- Select Save.
Creating a destination does not start exporting telemetry. To export Workers Logs or Workers Traces, configure OpenTelemetry export for your Worker. To export Cloudflare Traces, configure export for your domain.
Data may take several minutes to appear in Sentry.