Changelog
Custom fields raw and transformed values support
Custom Fields now support logging both raw and transformed values for request and response headers in the HTTP requests dataset.
These fields are configured per zone and apply to all Logpush jobs in that zone that include request headers, response headers. Each header can be logged in only one format—either raw or transformed—not both.
By default:
- Request headers are logged as raw values
- Response headers are logged as transformed values
These defaults can be overidden to suit your logging needs.
For more information refer to Custom fields documentation
One-click Logpush Setup with R2 Object Storage
We’ve streamlined the Logpush setup process by integrating R2 bucket creation directly into the Logpush workflow!
Now, you no longer need to navigate multiple pages to manually create an R2 bucket or copy credentials. With this update, you can seamlessly configure a Logpush job to R2 in just one click, reducing friction and making setup faster and easier.
This enhancement makes it easier for customers to adopt Logpush and R2.
For more details refer to our Logs documentation.

Cloudflare has introduced new fields two Gateway-related datasets in Cloudflare Logs:
-
Gateway HTTP:
ApplicationIDs
,ApplicationNames
,CategoryIDs
,CategoryNames
,DestinationIPContinentCode
,DestinationIPCountryCode
,ProxyEndpoint
,SourceIPContinentCode
,SourceIPCountryCode
,VirtualNetworkID
, andVirtualNetworkName
. -
Gateway Network:
ApplicationIDs
,ApplicationNames
,DestinationIPContinentCode
,DestinationIPCountryCode
,ProxyEndpoint
,SourceIPContinentCode
,SourceIPCountryCode
,TransportProtocol
,VirtualNetworkID
, andVirtualNetworkName
.
Was this helpful?
- Resources
- API
- New to Cloudflare?
- Products
- Sponsorships
- Open Source
- Support
- Help Center
- System Status
- Compliance
- GDPR
- Company
- cloudflare.com
- Our team
- Careers
- 2025 Cloudflare, Inc.
- Privacy Policy
- Terms of Use
- Report Security Issues
- Trademark