Stream Google Cloud load-balancer logs to Lume
Route external Application Load Balancer (Cloud CDN) logs to Lume via a Pub/Sub push subscription.
Install
1Add IP-free geo headers
On your external Application Load Balancer’s backend service, add custom request headers for country + ASN and enable request logging.
2Route logs to Pub/Sub
Create a Pub/Sub topic and a Log Router sink that routes the LB’s request logs to it.
3Push to Lume
Create a push subscription that POSTs each entry to https://in.lumetraffic.com/logs/gcp, sending the ingest token as an Authorization header (never in the URL).
Good to know
- For sites behind a Google Cloud external Application Load Balancer with Cloud CDN. Country and ASN ride along as IP-free custom request headers you add on the LB.
- Send the token as a header, not in the URL: a token in the query string is written verbatim into every access log along the path. The LB’s remoteIp optionally enables crawler verification (used transiently, never stored).
- Pub/Sub push sends one message per request, so very high-traffic LBs can hit the ingest rate limit. Best for low / medium volume for now.
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.
Google Cloud FAQ
What has to be in front of my site?
A Google Cloud external Application Load Balancer (with Cloud CDN). Its request logs flow through a Log Router sink to a Pub/Sub topic, and a push subscription delivers each entry to Lume.
Where does the ingest token go?
In an Authorization header on the push subscription, never in the URL, where it would be written verbatim into access logs. Lume dedupes on the log entry’s insertId.
Send your first Google Cloud event in minutes.
Free plan, one ingest token. See every human, bot, and AI agent, however you install.
Start for free →