Cloudflare lets customers filter and reshape logs before export

Cloudflare has made Transformers generally available in Logpush, letting customers filter, redact and reshape logs before they reach an external destination. The practical gain is control over what gets exported, without having to run a separate processing service just to tidy the data afterwards.

Cloudflare Watch analysis

What happened

Customers can write a SQL query for a Logpush dataset to remove unwanted records, redact sensitive fields, or change record structure by adding, renaming, removing or nesting fields. They can create and preview a Transformer in Cloudflare’s dashboard, or manage it through the API, then attach it to a compatible Logpush job using the same dataset. The output is NDJSON.

Cloudflare says Transformers are available on Free, Pro, Business and Enterprise plans. It describes the feature in its Logpush Transformers announcement.

Why it matters

Filtering before export can reduce the volume of data sent on to be ingested and stored. Redaction and reshaping can also help teams prepare records for security tools, analytics platforms and dashboards without maintaining a separate processing tier.

There is a useful safety detail: if a transformation fails, Cloudflare says Logpush does not send the untransformed batch or advance the delivery offset. Instead, it retries and reports errors, with persistent failures eventually leading to the job being disabled. That avoids quietly sending raw data where downstream systems expect filtered or redacted records.

Our read

This is the sort of infrastructure improvement that earns its keep by removing a chore, not by demanding applause. Teams can put a transformation in the export path and keep it close to the job it serves. The fail-closed behaviour is particularly important when redaction is part of the point.

What to watch

• Whether customers find the SQL preview and dataset-specific setup straightforward.
• How transformation failures and retries affect delivery for busy jobs.
• Whether filtering before export meaningfully reduces downstream data volume and cost.

Discussion spark: Would you rather transform and redact logs at the point of export, as Cloudflare proposes, or keep that processing in a separate service you control?

not affiliated with or endorsed by Cloudflare