Logs

Logpush is now available on all plans with usage-based pricing

Cloudflare Logpush is now available on Free, Pro, Business, and Enterprise plans with usage-based pricing. Free, Pro, and Business customers can enable Logpush through self-service. Enterprise customers continue to work with their account team.

Transformers are now generally available

for supported Logpush datasets on Free, Pro, Business, and Enterprise plans. Use SQL to filter records, reshape fields, redact sensitive values, compute new fields, or add metadata before Logpush delivers each batch.

Filter DDoS attack traffic from Logpush jobs

Logpush jobs can now exclude identified distributed denial-of-service (DDoS) attack traffic. This option reduces attack traffic in delivered logs.

Azure Functions-based Microsoft Sentinel connector deprecation

Cloudflare Enterprise customers using the Azure Functions-based Microsoft Sentinel connector must migrate to the Cloudflare for Microsoft Sentinel Codeless Connector Framework (CCF) connector by 2026-09-14.

New Logpush datasets and updated fields across multiple Logpush datasets in Cloudflare Logs

Cloudflare has updated Logpush datasets:

Per-zone post-quantum visibility in Logpush and Log Explorer

Cloudflare Radar publishes global statistics on post-quantum key agreement adoption across all Cloudflare traffic, but until now customers had no way to see the same measurement scoped to their own zones.

New WebSocket Analytics Logpush dataset

Enterprise customers can now push per-connection WebSocket analytics to any Logpush destination using the new websocket_analytics dataset.

Updated fields across multiple Logpush datasets in Cloudflare Logs

Cloudflare has updated Logpush datasets:

Account-scoped firewall events dataset in Logpush

Cloudflare Logpush now supports firewall events as an account-scoped dataset. Configure a single Logpush job at the account level to receive firewall events for every zone in the account, instead of creating and maintaining a separate job per zone.

New WebSocket Analytics Logpush dataset and updated fields

Cloudflare has updated Logpush datasets:

New Turnstile Events Logpush dataset in Cloudflare Logs

Cloudflare has updated Logpush datasets:

Updated fields across multiple Logpush datasets in Cloudflare Logs

Cloudflare has updated Logpush datasets:

New Logpush datasets and updated fields across multiple Logpush datasets in Cloudflare Logs

Cloudflare has updated Logpush datasets:

Logpush subrequest merging for HTTP requests

When a Cloudflare Worker intercepts a visitor request, it can dispatch additional outbound fetch calls called subrequests. By default, each subrequest generates its own log entry in Logpush, resulting in multiple log lines per visitor request.

Cloudflare Pipelines as a Logpush destination

Logpush has traditionally been great at delivering Cloudflare logs to a variety of destinations in JSON format. While JSON is flexible and easily readable, it can be inefficient to store and query at scale.

New TenantID and Firewall for AI fields in Logpush datasets

Cloudflare has added new fields to multiple Logpush datasets:

Logpush to BigQuery — Cloudflare dashboard support

You can now configure Logpush jobs to Google BigQuery directly from the Cloudflare dashboard, in addition to the existing API-based setup.

New ResponseTimeMs field in Gateway DNS Logpush dataset

Cloudflare has added a new field to the Gateway DNS Logpush dataset:

BigQuery as Logpush destination

Cloudflare Logpush now supports BigQuery as a native destination.

Logpush — More granular timestamps

Logpush now supports higher-precision timestamp formats for log output. You can configure jobs to output timestamps at millisecond or nanosecond precision. This is available in both the Logpush UI in the Cloudflare dashboard and the Logpush API.