Cloudflare Logpush

This guide configures logs. Replace YOUR_INGEST_KEY with your key on your server, never in a public example.

1. Create a Logpush HTTP destination

Use this body in Cloudflare Logpush job creation for your account. http_requests is also supported with its corresponding fields. Cloudflare encodes custom headers in destination_conf, so that configuration URL contains a credential and must be protected. The header_* parameters are consumed by Cloudflare, not used as receiver query authentication.

{
  "name": "siteqwality",
  "dataset": "workers_trace_events",
  "enabled": true,
  "destination_conf": "https://otlp.siteqwality.com/v1/cloudflare?header_Authorization=Bearer%20YOUR_INGEST_KEY",
  "max_upload_records": 1000
}

2. Verify the dataset and validation

Workers logs map ScriptName and EventTimestamp; HTTP requests map RayID and EdgeStartTimestamp. The receiver requires gzip bounds and accepts only the implemented datasets. Cloudflare minimum batch settings can exceed the receiver wire limit for large records; use a splitting bridge when batches cannot stay below 4,000,000 compressed bytes and 40,000,000 inflated bytes.

Allow the ownership validation request containing the content=test validation object. Enable the job, generate a Worker request and inspect Logpush delivery errors and Logs.

See your data

Open Logs, Traces or Metrics. New data usually shows up within a minute, and a page that says it is waiting for data switches to your data on its own. Nothing arriving? See what each status code means in failure handling.

Production checklist

Store the key in your platform secret mechanism, rotate it when exposed and remove test keys. Set a stable service.name and deployment.environment.name; avoid user IDs or unbounded values in metric labels. Prefer a persistent queue, bounded retries and exporter failure monitoring. Review redaction and processors before increasing traffic.