Send Cloudflare Logpush to Lume
For Enterprise Cloudflare zones that want zero code at the edge: batched request logs via Logpush.
Install
1Create a Logpush job
Point a Logpush job for the http_requests dataset at an HTTP destination on Lume, carrying the auth header via Logpush’s header_Authorization option.
2Select the fields
Select the request-log fields Lume needs and keep the default gzip + NDJSON output.
3Verify
Logpush delivers in batches every few minutes, and events appear on your dashboard shortly after.
Good to know
- Enterprise-tier Cloudflare only. Most Cloudflare users want the Worker instead: it’s real-time, works on every plan, and is cheaper. Reach for Logpush only if you specifically want no code at the edge.
- Cloudflare’s edge fields give country + ASN with no IP. Optionally select ClientIP to enable crawler verification (used transiently, never stored); RayID is used for dedupe.
- Batched, not real-time: Logpush trades latency for zero edge code.
Works with the rest of your stack
Lume is CDN-agnostic and server-side. This is one of several install paths, all feeding the same dashboard. Mix and match across hosts, or move providers without losing your history.
Cloudflare Logpush FAQ
Do I need Cloudflare Enterprise?
Yes, Logpush is an Enterprise feature. On any other plan (or if you just want real-time data), use the Cloudflare Worker instead: it works on every plan.
Logpush or the Worker?
The Worker is real-time, works on every plan, and is cheaper. Logpush’s only advantage is zero code at the edge on Enterprise zones.
Send your first Cloudflare Logpush event in minutes.
Free plan, one ingest token. See every human, bot, and AI agent, however you install.
Start for free →