Cloudflare Logpush gets new fields: trace matched rules and header changes right from your logs!

Hi there, it's Shiichan! Today I found a small but genuinely handy logging update, so let me walk you through it.

Cloudflare Changelog developers.cloudflare.com

What was announced?

Over on the Cloudflare Changelog, there's news that several Logpush datasets got new fields. The datasets involved are DEX Device State Events, Gateway HTTP, and HTTP requests, three in total.

The story so far

Logpush is the mechanism that ships logs of events happening on Cloudflare out to your external storage or analytics backend. The fields inside those logs are defined ahead of time, so when the value you want isn't there, you end up thinking "I really wish I'd captured that too!" when you go to analyze things later.

What changes

With these new fields, you can now trace device registration profiles, the rules applied to a request, and even the headers Gateway rewrote, all straight from your logs. When you're doing audits or troubleshooting, it becomes much easier to reconstruct what actually happened at a finer level of detail.

Dive Deep

Here are the fields that were added.

• DeviceRegistrationProfileID on DEX Device State Events
• AddedHeaders, DeletedHeaders, and SetHeaders on Gateway HTTP
• MatchedRules on HTTP requests

The Gateway HTTP header fields record the headers that a policy added, deleted, or overwrote separately, so you can see which rule touched a request and how. The detailed meaning of each field is documented in the Logpush datasets reference. You can find out how to use Logpush itself from the Logs page.

Wrap-up

• Cloudflare added fields to three Logpush datasets
• DeviceRegistrationProfileID on DEX Device State Events, AddedHeaders/DeletedHeaders/SetHeaders on Gateway HTTP, and MatchedRules on HTTP requests
• You can now trace applied rules and rewritten headers right from your logs

If you're on an ops team shipping logs out for audits or analysis, this is a quiet update that pays off nicely!