Filter, reshape, and redact logs before export with Transformers
- ID
- 34539
- Status
- summarized
- Published
- 12 Oct 2026, 10:44 PM
- Fetched
- 13 Oct 2026, 12:35 AM
- Provider
- Cloudflare Blog
- Category
- infrastructure
- Original URL
- https://blog.cloudflare.com/transformers-on-logpush/
- Source URL
- https://blog.cloudflare.com/rss/
Summary
- Score
- 6.0
- Created
- 13 Oct 2026, 12:35 AM
- Tags
- Audience
- developersdatabase_learnerssaas_startup_founders
What happened
Cloudflare says Logpush is now available on all self-serve plans and its Transformers feature is generally available, as part of eight Observability updates from Birthday Week. Transformers let teams attach a dataset-specific SQL query to a compatible NDJSON Logpush job to filter records with WHERE, redact sensitive fields, and add, rename, remove, or nest fields before export. They can be created, previewed, and managed via Transformer Studio or the API, with each update versioned.
Why it matters
If you export Cloudflare logs to a SIEM, analytics platform, or object storage, you can now redact sensitive fields and drop records like health checks before they leave Logpush instead of running a separate processing service or paying to ingest and store discarded logs. Test it with preview/API on a compatible NDJSON job; the excerpt does not include pricing, limits, or the full SQL example, so validate behavior and performance yourself.
Discussion angle
Ask who currently runs a separate log-filtering service and what they would move into Logpush first: PII redaction, health-check filtering, or schema normalization across CDNs. Compare that with the trade-offs of external processing for cost, compliance, and debuggability.