Logs

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. With subrequest merging enabled,…

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. With this release, you can now…

Cloudflare has added new fields to multiple Logpush datasets: TenantID field The following Gateway and Zero Trust datasets now include a TenantID field: Gateway DNS: Identifies the tenant ID of the DNS request, if it exists. Gateway HTTP: Identifies the…

Cloudflare has added a new field to the Gateway DNS Logpush dataset: ResponseTimeMs: Total response time of the DNS request in milliseconds. For the complete field definitions, refer to Gateway DNS dataset.Source: Cloudflare Latest Posts

Cloudflare has added new fields across multiple Logpush datasets: New dataset MCP Portal Logs: A new dataset with fields including ClientCountry, ClientIP, ColoCode, Datetime, Error, Method, PortalAUD, PortalID, PromptGetName, ResourceReadURI, ServerAUD, ServerID, ServerResponseDurationMs, ServerURL, SessionID, Success, ToolCallName, UserEmail, and UserID.…

Cloudflare Logpush now supports SentinelOne as a native destination. Logs from Cloudflare can be sent to SentinelOne AI SIEM via Logpush. The destination can be configured through the Logpush UI in the Cloudflare dashboard or by using the Logpush API.…