Stream Fastly logs to Lume
Point Fastly’s Real-Time Log Streaming straight at Lume: config-only, no code, no extra infrastructure.
Install
1Add an HTTPS logging endpoint
In the Fastly UI, add an HTTPS endpoint pointing at https://in.lumetraffic.com/logs/fastly (POST, application/json) with an Authorization: Bearer header.
2Paste Lume’s log format
Use Lume’s JSON log format, which maps Fastly’s VCL variables to Lume’s fields.
3Activate & verify
Activate the new version of your service and send a request, and events appear on your dashboard within a minute.
Good to know
- Real-Time Log Streaming POSTs a JSON line per request directly to Lume: no Kinesis, no queue, nothing to run. Works for VCL and Compute services alike.
- Fastly’s edge geo gives country and ASN with no IP. Optionally add a client_ip field to enable crawler verification (used transiently, never stored).
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.
Fastly FAQ
Do I have to run any code or infrastructure?
No. Setup is entirely in the Fastly UI (or one Terraform block): Fastly POSTs the logs straight to Lume’s /logs endpoint, with nothing to deploy or maintain.
Can Fastly logs verify crawlers?
Yes, if you add the optional client_ip field to the log format. Without it, agents are identified by user-agent + catalog and shown as not network-verified (never falsely flagged).
Send your first Fastly event in minutes.
Free plan, one ingest token. See every human, bot, and AI agent, however you install.
Start for free →