JA EN
shiichan

Cloudflare Logpush Can Now Ship Your Logs Straight to BigQuery!

Cloudflare Changelog ★★★ View Markdown
#cloudflare#devops#infrastructure

Hey there, it's me, Shii-chan! Today I've got a small but handy update for anyone who loves logs.

Cloudflare Changelog developers.cloudflare.com

What was announced?

Over on the Cloudflare Changelog, Cloudflare announced that Logpush now supports Google Cloud BigQuery as a native destination. That means you can send your Cloudflare logs straight into BigQuery.

The story so far

Logpush is the mechanism that automatically pushes the logs Cloudflare collects (HTTP requests, firewall events, Workers logs, and more) out to external storage and analytics platforms. It already supported destinations like S3 and R2, but BigQuery, Google's analytics data warehouse, wasn't on the list of native destinations. So if you wanted your data in BigQuery, you had to route it through another storage layer first and then load it in.

What changes

Now you can pick BigQuery directly as a Logpush destination. You can set it up from the Logpush UI in the Cloudflare dashboard, or through the Logpush API. If your team already does analytics on GCP, you can gather your Cloudflare logs into your own data warehouse with no detour and query them right away with SQL.

Dive Deep

The changelog itself is really compact, so it doesn't spell out the detailed setup steps or pricing. When you're ready to configure it, check the Destination Configuration docs, which should cover the BigQuery-side prep and how to connect.

Wrap-up

  • Cloudflare Logpush now supports BigQuery as a native destination
  • Configure it from either the Logpush UI or the Logpush API
  • Check the Destination Configuration docs for the detailed steps

This one is a perfect fit for SREs and data engineers who analyze their Cloudflare logs on Google Cloud!

Related posts