<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Cloudflare changelogs | Logs</title><description>Cloudflare changelogs for Logs</description><link>https://developers.cloudflare.com/changelog/</link><item><title>logpush, Logs - Account-scoped HTTP request logs in Logpush</title><link>https://developers.cloudflare.com/changelog/post/2026-10-21-account-scoped-http-requests/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-10-21-account-scoped-http-requests/</guid><description>&lt;p&gt;Cloudflare Logpush now supports HTTP request logs as an &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/http_requests/&quot;&gt;account-scoped dataset&lt;/a&gt;. Use one job to deliver logs for every zone in an account instead of maintaining a separate job for each zone.&lt;/p&gt;
&lt;p&gt;Create the job at the account level in the Cloudflare dashboard or through the Logpush API. The &lt;code&gt;ZoneName&lt;/code&gt; field identifies the source zone in each log entry.&lt;/p&gt;
&lt;p&gt;Custom fields remain configured per zone. An account-scoped job honors the custom fields configuration for each zone but does not support account-wide custom fields configuration.&lt;/p&gt;
&lt;p&gt;For setup details, refer to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/api-configuration/&quot;&gt;API configuration&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate><product>logpush</product><category>logpush</category><category>Logs</category></item><item><title>logpush, Logs - Logpush is now available on all plans with usage-based pricing</title><link>https://developers.cloudflare.com/changelog/post/2026-09-30-logpush-usage-based-pricing/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-09-30-logpush-usage-based-pricing/</guid><description>&lt;p&gt;Cloudflare Logpush is now available on Free, Pro, Business, and Enterprise plans with usage-based pricing. Free, Pro, and Business customers can enable Logpush through self-service. Enterprise customers continue to work with their account team. Logpush Transformers are also now generally available.&lt;/p&gt;
&lt;p&gt;Each account receives included monthly usage before charges apply:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Internal exports&lt;/strong&gt;: 25 GB per month, then $0.03 per additional GB.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;External exports&lt;/strong&gt;: 25 GB per month, then $0.10 per additional GB.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Transformations&lt;/strong&gt;: 1 GB per month, then $0.04 per additional GB.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;R2 and Pipelines use the internal destination rate. All other destinations use the external destination rate.&lt;/p&gt;
&lt;p&gt;Existing Enterprise contracts retain their current Logpush pricing through renewal. Workers Logpush for Workers Trace Events retains request-based pricing, and OpenTelemetry destinations retain event-based Workers Observability pricing.&lt;/p&gt;
&lt;p&gt;For complete rates, measurement details, and billing examples, refer to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/pricing/&quot;&gt;Logpush pricing&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Wed, 30 Sep 2026 00:00:00 GMT</pubDate><product>logpush</product><category>logpush</category><category>Logs</category></item><item><title>logpush, Logs - Transformers are now generally available</title><link>https://developers.cloudflare.com/changelog/post/2026-09-30-transformers-ga/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-09-30-transformers-ga/</guid><description>&lt;p&gt;Transformers are now generally available for supported Logpush datasets on Free, Pro, Business, and Enterprise plans. Use SQL to filter records, reshape fields, redact sensitive values, compute new fields, or add metadata before Logpush delivers each batch.&lt;/p&gt;
&lt;p&gt;Create and preview Transformers in Transformer Studio or through the Cloudflare API, then attach them to eligible account-scoped or zone-scoped Logpush jobs that use NDJSON output. Cloudflare validates each query against the dataset schema before saving it.&lt;/p&gt;
&lt;p&gt;Each account includes 1 GB of transformation input per month. Additional input costs $0.04 per GB. For setup instructions, supported SQL, limits, and examples, refer to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/transformers/&quot;&gt;Transformers&lt;/a&gt;. For billing details, refer to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/pricing/&quot;&gt;Logpush pricing&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Wed, 30 Sep 2026 00:00:00 GMT</pubDate><product>logpush</product><category>logpush</category><category>Logs</category></item><item><title>logpush, Logs - Filter DDoS attack traffic from Logpush jobs</title><link>https://developers.cloudflare.com/changelog/post/2026-09-18-filter-ddos-attack-traffic/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-09-18-filter-ddos-attack-traffic/</guid><description>&lt;p&gt;Logpush jobs can now exclude identified distributed denial-of-service (DDoS) attack traffic. This option reduces attack traffic in delivered logs.&lt;/p&gt;
&lt;p&gt;It supports the &lt;code&gt;http_requests&lt;/code&gt;, &lt;code&gt;firewall_events&lt;/code&gt;, and &lt;code&gt;network_analytics_logs&lt;/code&gt; datasets.&lt;/p&gt;
&lt;p&gt;In the dashboard, select &lt;strong&gt;Exclude DDoS attack traffic&lt;/strong&gt; under &lt;strong&gt;Advanced Options&lt;/strong&gt;. With the API, add this field to a job request:&lt;/p&gt;
&lt;figure class=&quot;nb-code-figure&quot; data-nb-lang=&quot;json&quot;&gt;&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark nb-shiki-c6xiwz&quot; tabindex=&quot;0&quot; data-language=&quot;json&quot; data-nb-lang=&quot;json&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;nb-shiki-140thh&quot;&gt;{&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;nb-shiki-dzsirb&quot;&gt;	&quot;filter_attack_traffic&quot;&lt;/span&gt;&lt;span class=&quot;nb-shiki-140thh&quot;&gt;: &lt;/span&gt;&lt;span class=&quot;nb-shiki-dzsirb&quot;&gt;true&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;nb-shiki-140thh&quot;&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;
&lt;p&gt;For more information, refer to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/api-configuration/#ddos-attack-traffic&quot;&gt;API configuration&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Fri, 18 Sep 2026 00:00:00 GMT</pubDate><product>logpush</product><category>logpush</category><category>Logs</category></item><item><title>Logpush Connectors, Logs - Azure Functions-based Microsoft Sentinel connector deprecation</title><link>https://developers.cloudflare.com/changelog/post/2026-08-26-sentinel-functions-connector-deprecation/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-08-26-sentinel-functions-connector-deprecation/</guid><description>&lt;p&gt;Cloudflare Enterprise customers using the &lt;a href=&quot;https://marketplace.microsoft.com/en-us/product/cloudflare.cloudflare_sentinel?tab=Overview&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Azure Functions-based Microsoft Sentinel connector&lt;span class=&quot;external-link&quot;&gt; ↗︎&lt;/span&gt;&lt;/a&gt; must migrate to the &lt;a href=&quot;https://marketplace.microsoft.com/en-us/product/cloudflare.azure-sentinel-solution-cloudflare-ccf?tab=Overview&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Cloudflare for Microsoft Sentinel Codeless Connector Framework (CCF) connector&lt;span class=&quot;external-link&quot;&gt; ↗︎&lt;/span&gt;&lt;/a&gt; by 2026-09-14.&lt;/p&gt;
&lt;p&gt;Microsoft is deprecating the Azure Monitor HTTP Data Collector API. Support for the API ends on 2026-09-14. As a result, Cloudflare will no longer maintain the Azure Functions-based connector after that date.&lt;/p&gt;
&lt;p&gt;To migrate, follow the &lt;a href=&quot;https://developers.cloudflare.com/analytics/analytics-integrations/sentinel/&quot;&gt;Microsoft Sentinel integration setup guide&lt;/a&gt;.&lt;/p&gt;
&lt;div tabindex=&quot;-1&quot; class=&quot;heading-wrapper level-h4&quot;&gt;&lt;h4 id=&quot;additional-resources&quot;&gt;Additional resources&lt;/h4&gt;&lt;a class=&quot;anchor-link&quot; href=&quot;#additional-resources&quot;&gt;&lt;span aria-hidden=&quot;true&quot; class=&quot;anchor-icon&quot;&gt;&lt;svg width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 24 24&quot;&gt;&lt;path fill=&quot;currentcolor&quot; d=&quot;m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://marketplace.microsoft.com/en-us/product/azure-application/cloudflare.azure-sentinel-solution-cloudflare-ccf?tab=Overview&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Download Cloudflare&apos;s CCF Sentinel Solution&lt;span class=&quot;external-link&quot;&gt; ↗︎&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://learn.microsoft.com/en-us/azure/sentinel/datalake/sentinel-lake-overview&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Microsoft Sentinel data lake overview&lt;span class=&quot;external-link&quot;&gt; ↗︎&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://learn.microsoft.com/en-us/azure/sentinel/create-codeless-connector&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;About the CCF platform&lt;span class=&quot;external-link&quot;&gt; ↗︎&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For more information, refer to Microsoft&apos;s &lt;a href=&quot;https://learn.microsoft.com/en-us/previous-versions/azure/azure-monitor/logs/data-collector-api?tabs=powershell&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Azure Monitor HTTP Data Collector API deprecation notice&lt;span class=&quot;external-link&quot;&gt; ↗︎&lt;/span&gt;&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Wed, 26 Aug 2026 00:00:00 GMT</pubDate><product>Logpush Connectors</product><category>Logpush Connectors</category><category>Logs</category></item><item><title>Logs - New Logpush datasets and updated fields across multiple Logpush datasets in Cloudflare Logs</title><link>https://developers.cloudflare.com/changelog/post/2026-08-20-log-fields-updated/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-08-20-log-fields-updated/</guid><description>&lt;p&gt;Cloudflare has updated &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/&quot;&gt;Logpush datasets&lt;/a&gt;:&lt;/p&gt;
&lt;div tabindex=&quot;-1&quot; class=&quot;heading-wrapper level-h4&quot;&gt;&lt;h4 id=&quot;new-datasets&quot;&gt;New datasets&lt;/h4&gt;&lt;a class=&quot;anchor-link&quot; href=&quot;#new-datasets&quot;&gt;&lt;span aria-hidden=&quot;true&quot; class=&quot;anchor-icon&quot;&gt;&lt;svg width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 24 24&quot;&gt;&lt;path fill=&quot;currentcolor&quot; d=&quot;m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Account Abuse Protection Events&lt;/strong&gt;: A new dataset with fields including &lt;code&gt;AuthenticationIdentityProvider&lt;/code&gt;, &lt;code&gt;AuthenticationMethod&lt;/code&gt;, &lt;code&gt;AuthenticationStatus&lt;/code&gt;, &lt;code&gt;BotScore&lt;/code&gt;, &lt;code&gt;ClientASN&lt;/code&gt;, &lt;code&gt;ClientCity&lt;/code&gt;, &lt;code&gt;ClientCountry&lt;/code&gt;, &lt;code&gt;ClientIP&lt;/code&gt;, &lt;code&gt;Email&lt;/code&gt;, &lt;code&gt;EphemeralID&lt;/code&gt;, &lt;code&gt;EventSource&lt;/code&gt;, &lt;code&gt;EventType&lt;/code&gt;, &lt;code&gt;FraudEmailRisk&lt;/code&gt;, &lt;code&gt;Host&lt;/code&gt;, &lt;code&gt;JA4&lt;/code&gt;, &lt;code&gt;RayID&lt;/code&gt;, &lt;code&gt;Timestamp&lt;/code&gt;, &lt;code&gt;UserAgent&lt;/code&gt;, and &lt;code&gt;UserID&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Magic BGP Logs&lt;/strong&gt;: A new dataset with fields including &lt;code&gt;Direction&lt;/code&gt;, &lt;code&gt;EventData&lt;/code&gt;, &lt;code&gt;EventKind&lt;/code&gt;, &lt;code&gt;EventTimestamp&lt;/code&gt;, &lt;code&gt;TunnelID&lt;/code&gt;, and &lt;code&gt;TunnelName&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;div tabindex=&quot;-1&quot; class=&quot;heading-wrapper level-h4&quot;&gt;&lt;h4 id=&quot;updated-fields-in-existing-datasets&quot;&gt;Updated fields in existing datasets&lt;/h4&gt;&lt;a class=&quot;anchor-link&quot; href=&quot;#updated-fields-in-existing-datasets&quot;&gt;&lt;span aria-hidden=&quot;true&quot; class=&quot;anchor-icon&quot;&gt;&lt;svg width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 24 24&quot;&gt;&lt;path fill=&quot;currentcolor&quot; d=&quot;m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Firewall events&lt;/strong&gt; (added): &lt;code&gt;AISecurityCustomTopicCategories&lt;/code&gt;, &lt;code&gt;WAFRequestSignatureCategories&lt;/code&gt;, and &lt;code&gt;WAFRequestSignatureRefs&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Gateway HTTP&lt;/strong&gt; (added): &lt;code&gt;ExperimentalFeatures&lt;/code&gt; and &lt;code&gt;PackageInfo&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;HTTP requests&lt;/strong&gt; (added): &lt;code&gt;AISecurityCustomTopicCategories&lt;/code&gt;, &lt;code&gt;ClientTLSKeyExchangeGroup&lt;/code&gt;, &lt;code&gt;WAFRequestSignatureCategories&lt;/code&gt;, and &lt;code&gt;WAFRequestSignatureRefs&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For the complete field definitions for each dataset, refer to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/&quot;&gt;Logpush datasets&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>Logs, Log Explorer - Per-zone post-quantum visibility in Logpush and Log Explorer</title><link>https://developers.cloudflare.com/changelog/post/2026-08-20-pqc-key-exchange-visibility/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-08-20-pqc-key-exchange-visibility/</guid><description>&lt;p&gt;&lt;a href=&quot;https://radar.cloudflare.com/post-quantum&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Cloudflare Radar&lt;span class=&quot;external-link&quot;&gt; ↗︎&lt;/span&gt;&lt;/a&gt; publishes global statistics on post-quantum key agreement adoption across all Cloudflare traffic, but until now customers had no way to see the same measurement scoped to their own zones. This is now possible because the &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/zone/http_requests/&quot;&gt;&lt;code&gt;http_requests&lt;/code&gt;&lt;/a&gt; Logpush dataset — also queryable in &lt;a href=&quot;https://developers.cloudflare.com/observability/logs/log-explorer/&quot;&gt;Log Explorer&lt;/a&gt; — includes a new &lt;code&gt;ClientTLSKeyExchangeGroup&lt;/code&gt; field.&lt;/p&gt;
&lt;p&gt;The field reports the TLS key exchange group negotiated on the client-to-Cloudflare connection, by group name. Post-quantum connections appear as &lt;code&gt;X25519MLKEM768&lt;/code&gt;, and classical connections appear as &lt;code&gt;X25519&lt;/code&gt;, &lt;code&gt;P-256&lt;/code&gt;, or another named group. A value of &lt;code&gt;UNK&lt;/code&gt; means the group could not be determined, and &lt;code&gt;NONE&lt;/code&gt; means either RSA key exchange was used or TLS was not used.&lt;/p&gt;
&lt;p&gt;With this field, you can build per-zone reports showing what percentage of your inbound HTTPS traffic is protected by post-quantum key agreement, break the number down by hostname, path, user agent, or country, and push the data into your SIEM via any &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/enable-destinations/&quot;&gt;Logpush destination&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category><category>Log Explorer</category></item><item><title>Logs - New WebSocket Analytics Logpush dataset</title><link>https://developers.cloudflare.com/changelog/post/2026-07-07-websocket-analytics-dataset/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-07-07-websocket-analytics-dataset/</guid><description>&lt;p&gt;Enterprise customers can now push per-connection WebSocket analytics to any &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/enable-destinations/&quot;&gt;Logpush destination&lt;/a&gt; using the new &lt;code&gt;websocket_analytics&lt;/code&gt; dataset. Each log record is emitted when a WebSocket connection closes and includes fields that were previously only available to Cloudflare engineers via internal tooling.&lt;/p&gt;
&lt;p&gt;Key fields include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;ConnectionCloseReason&lt;/code&gt;&lt;/strong&gt; — why the connection ended: &lt;code&gt;peerReset&lt;/code&gt;, &lt;code&gt;peerNoError&lt;/code&gt;, &lt;code&gt;timedOut&lt;/code&gt;, &lt;code&gt;upstreamReset&lt;/code&gt;, &lt;code&gt;protocolViolation&lt;/code&gt;, &lt;code&gt;unspecifiedError&lt;/code&gt;, or &lt;code&gt;none&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;ConnectionCloseSource&lt;/code&gt;&lt;/strong&gt; — which side initiated the close: &lt;code&gt;upstream&lt;/code&gt;, &lt;code&gt;downstream&lt;/code&gt;, &lt;code&gt;me&lt;/code&gt;, or &lt;code&gt;both&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;ConnectionTransportCloseCode&lt;/code&gt;&lt;/strong&gt; — the TLS alert code or TCP-level close code for additional precision.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;RayID&lt;/code&gt;&lt;/strong&gt; — correlate WebSocket connection events with your existing HTTP Request logs.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The dataset also includes directional byte counts (&lt;code&gt;BytesSentClient&lt;/code&gt;, &lt;code&gt;BytesReceivedClient&lt;/code&gt;, &lt;code&gt;BytesSentOrigin&lt;/code&gt;, &lt;code&gt;BytesReceivedOrigin&lt;/code&gt;), connection timestamps, client IP, colo code, and request metadata from the original WebSocket upgrade.&lt;/p&gt;
&lt;p&gt;This data lets you build alerts on connection close patterns — for example, detecting spikes in TCP resets (&lt;code&gt;ConnectionCloseReason == &quot;peerReset&quot;&lt;/code&gt;) grouped by host and data center — directly in your existing log analysis tools.&lt;/p&gt;
&lt;p&gt;For the full list of available fields, refer to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/zone/websocket_analytics/&quot;&gt;WebSocket Analytics&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>Logs - Updated fields across multiple Logpush datasets in Cloudflare Logs</title><link>https://developers.cloudflare.com/changelog/post/2026-07-02-log-fields-updated/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-07-02-log-fields-updated/</guid><description>&lt;p&gt;Cloudflare has updated &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/&quot;&gt;Logpush datasets&lt;/a&gt;:&lt;/p&gt;
&lt;div tabindex=&quot;-1&quot; class=&quot;heading-wrapper level-h4&quot;&gt;&lt;h4 id=&quot;updated-fields-in-existing-datasets&quot;&gt;Updated fields in existing datasets&lt;/h4&gt;&lt;a class=&quot;anchor-link&quot; href=&quot;#updated-fields-in-existing-datasets&quot;&gt;&lt;span aria-hidden=&quot;true&quot; class=&quot;anchor-icon&quot;&gt;&lt;svg width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 24 24&quot;&gt;&lt;path fill=&quot;currentcolor&quot; d=&quot;m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Gateway DNS&lt;/strong&gt; (added): &lt;code&gt;AppliedMaxTTL&lt;/code&gt; and &lt;code&gt;UpstreamRecordTTLs&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Gateway HTTP&lt;/strong&gt; (added): &lt;code&gt;Warnings&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;HTTP requests&lt;/strong&gt; (added): &lt;code&gt;CacheLockWaitedMs&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For the complete field definitions for each dataset, refer to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/&quot;&gt;Logpush datasets&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Thu, 02 Jul 2026 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>Logs - Account-scoped firewall events dataset in Logpush</title><link>https://developers.cloudflare.com/changelog/post/2026-06-30-account-level-firewall-events/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-06-30-account-level-firewall-events/</guid><description>&lt;p&gt;Cloudflare Logpush now supports &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/firewall_events/&quot;&gt;firewall events as an account-scoped dataset&lt;/a&gt;. Configure a single Logpush job at the account level to receive firewall events for every zone in the account, instead of creating and maintaining a separate job per zone.&lt;/p&gt;
&lt;p&gt;The dataset includes a new &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/firewall_events/#zonename&quot;&gt;&lt;code&gt;ZoneName&lt;/code&gt;&lt;/a&gt; field so you can identify which zone each event came from when consuming logs in your downstream pipeline.&lt;/p&gt;
&lt;div tabindex=&quot;-1&quot; class=&quot;heading-wrapper level-h4&quot;&gt;&lt;h4 id=&quot;whats-available&quot;&gt;What&apos;s available&lt;/h4&gt;&lt;a class=&quot;anchor-link&quot; href=&quot;#whats-available&quot;&gt;&lt;span aria-hidden=&quot;true&quot; class=&quot;anchor-icon&quot;&gt;&lt;svg width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 24 24&quot;&gt;&lt;path fill=&quot;currentcolor&quot; d=&quot;m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;A new account-scoped &lt;code&gt;firewall_events&lt;/code&gt; dataset, configurable via the &lt;a href=&quot;https://developers.cloudflare.com/api/resources/logpush/subresources/jobs/&quot;&gt;Logpush API&lt;/a&gt; or the Cloudflare dashboard.&lt;/li&gt;
&lt;li&gt;The same fields and filter expressions supported by the existing &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/zone/firewall_events/&quot;&gt;zone-scoped firewall events dataset&lt;/a&gt;, plus the new &lt;code&gt;ZoneName&lt;/code&gt; field.&lt;/li&gt;
&lt;li&gt;Support for all existing Logpush destinations.&lt;/li&gt;
&lt;/ul&gt;</description><pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>Logs - New WebSocket Analytics Logpush dataset and updated fields</title><link>https://developers.cloudflare.com/changelog/post/2026-06-24-log-fields-updated/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-06-24-log-fields-updated/</guid><description>&lt;p&gt;Cloudflare has updated &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/&quot;&gt;Logpush datasets&lt;/a&gt;:&lt;/p&gt;
&lt;div tabindex=&quot;-1&quot; class=&quot;heading-wrapper level-h4&quot;&gt;&lt;h4 id=&quot;new-datasets&quot;&gt;New datasets&lt;/h4&gt;&lt;a class=&quot;anchor-link&quot; href=&quot;#new-datasets&quot;&gt;&lt;span aria-hidden=&quot;true&quot; class=&quot;anchor-icon&quot;&gt;&lt;svg width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 24 24&quot;&gt;&lt;path fill=&quot;currentcolor&quot; d=&quot;m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;WebSocket Analytics&lt;/strong&gt;: A new dataset with fields including &lt;code&gt;BytesReceivedClient&lt;/code&gt;, &lt;code&gt;BytesReceivedOrigin&lt;/code&gt;, &lt;code&gt;BytesSentClient&lt;/code&gt;, &lt;code&gt;BytesSentOrigin&lt;/code&gt;, &lt;code&gt;ClientASN&lt;/code&gt;, &lt;code&gt;ClientIP&lt;/code&gt;, &lt;code&gt;ClientRequestHost&lt;/code&gt;, &lt;code&gt;ClientRequestPath&lt;/code&gt;, &lt;code&gt;ClientRequestUserAgent&lt;/code&gt;, &lt;code&gt;ColoCode&lt;/code&gt;, &lt;code&gt;ConnectionCloseReason&lt;/code&gt;, &lt;code&gt;ConnectionCloseSource&lt;/code&gt;, &lt;code&gt;ConnectionID&lt;/code&gt;, &lt;code&gt;ConnectionTransportCloseCode&lt;/code&gt;, &lt;code&gt;EdgeEndTimestamp&lt;/code&gt;, &lt;code&gt;EdgeStartTimestamp&lt;/code&gt;, and &lt;code&gt;RayID&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;div tabindex=&quot;-1&quot; class=&quot;heading-wrapper level-h4&quot;&gt;&lt;h4 id=&quot;updated-fields-in-existing-datasets&quot;&gt;Updated fields in existing datasets&lt;/h4&gt;&lt;a class=&quot;anchor-link&quot; href=&quot;#updated-fields-in-existing-datasets&quot;&gt;&lt;span aria-hidden=&quot;true&quot; class=&quot;anchor-icon&quot;&gt;&lt;svg width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 24 24&quot;&gt;&lt;path fill=&quot;currentcolor&quot; d=&quot;m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Firewall events&lt;/strong&gt; (added): &lt;code&gt;ZoneName&lt;/code&gt;. The Firewall events dataset is now also available for &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/firewall_events/&quot;&gt;account-scope Logpush&lt;/a&gt;, in addition to the existing zone scope.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Email Security Alerts&lt;/strong&gt; (added): &lt;code&gt;BCC&lt;/code&gt;, &lt;code&gt;DKIMResult&lt;/code&gt;, &lt;code&gt;DMARCPolicy&lt;/code&gt;, &lt;code&gt;DMARCResult&lt;/code&gt;, and &lt;code&gt;SPFResult&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For the complete field definitions for each dataset, refer to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/&quot;&gt;Logpush datasets&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>Logs - New Turnstile Events Logpush dataset in Cloudflare Logs</title><link>https://developers.cloudflare.com/changelog/post/2026-06-01-log-fields-updated/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-06-01-log-fields-updated/</guid><description>&lt;p&gt;Cloudflare has updated &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/&quot;&gt;Logpush datasets&lt;/a&gt;:&lt;/p&gt;
&lt;div tabindex=&quot;-1&quot; class=&quot;heading-wrapper level-h4&quot;&gt;&lt;h4 id=&quot;new-datasets&quot;&gt;New datasets&lt;/h4&gt;&lt;a class=&quot;anchor-link&quot; href=&quot;#new-datasets&quot;&gt;&lt;span aria-hidden=&quot;true&quot; class=&quot;anchor-icon&quot;&gt;&lt;svg width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 24 24&quot;&gt;&lt;path fill=&quot;currentcolor&quot; d=&quot;m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Turnstile Events&lt;/strong&gt;: A new dataset with fields including &lt;code&gt;ASN&lt;/code&gt;, &lt;code&gt;Action&lt;/code&gt;, &lt;code&gt;BrowserMajor&lt;/code&gt;, &lt;code&gt;BrowserName&lt;/code&gt;, &lt;code&gt;ClientIP&lt;/code&gt;, &lt;code&gt;CountryCode&lt;/code&gt;, &lt;code&gt;EventType&lt;/code&gt;, &lt;code&gt;Hostname&lt;/code&gt;, &lt;code&gt;OSMajor&lt;/code&gt;, &lt;code&gt;OSName&lt;/code&gt;, &lt;code&gt;Sitekey&lt;/code&gt;, &lt;code&gt;Timestamp&lt;/code&gt;, and &lt;code&gt;UserAgent&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For the complete field definitions for each dataset, refer to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/&quot;&gt;Logpush datasets&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Mon, 01 Jun 2026 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>Logs - Updated fields across multiple Logpush datasets in Cloudflare Logs</title><link>https://developers.cloudflare.com/changelog/post/2026-05-29-log-fields-updated/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-05-29-log-fields-updated/</guid><description>&lt;p&gt;Cloudflare has updated &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/&quot;&gt;Logpush datasets&lt;/a&gt;:&lt;/p&gt;
&lt;div tabindex=&quot;-1&quot; class=&quot;heading-wrapper level-h4&quot;&gt;&lt;h4 id=&quot;updated-fields-in-existing-datasets&quot;&gt;Updated fields in existing datasets&lt;/h4&gt;&lt;a class=&quot;anchor-link&quot; href=&quot;#updated-fields-in-existing-datasets&quot;&gt;&lt;span aria-hidden=&quot;true&quot; class=&quot;anchor-icon&quot;&gt;&lt;svg width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 24 24&quot;&gt;&lt;path fill=&quot;currentcolor&quot; d=&quot;m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;DEX Device State Events&lt;/strong&gt; (added): &lt;code&gt;DeviceRegistrationProfileID&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Gateway HTTP&lt;/strong&gt; (added): &lt;code&gt;AddedHeaders&lt;/code&gt;, &lt;code&gt;DeletedHeaders&lt;/code&gt;, and &lt;code&gt;SetHeaders&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;HTTP requests&lt;/strong&gt; (added): &lt;code&gt;MatchedRules&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For the complete field definitions for each dataset, refer to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/&quot;&gt;Logpush datasets&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>Logs - New Logpush datasets and updated fields across multiple Logpush datasets in Cloudflare Logs</title><link>https://developers.cloudflare.com/changelog/post/2026-05-13-log-fields-updated/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-05-13-log-fields-updated/</guid><description>&lt;p&gt;Cloudflare has updated &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/&quot;&gt;Logpush datasets&lt;/a&gt;:&lt;/p&gt;
&lt;div tabindex=&quot;-1&quot; class=&quot;heading-wrapper level-h4&quot;&gt;&lt;h4 id=&quot;new-datasets&quot;&gt;New datasets&lt;/h4&gt;&lt;a class=&quot;anchor-link&quot; href=&quot;#new-datasets&quot;&gt;&lt;span aria-hidden=&quot;true&quot; class=&quot;anchor-icon&quot;&gt;&lt;svg width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 24 24&quot;&gt;&lt;path fill=&quot;currentcolor&quot; d=&quot;m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Email Security Post-Delivery Events&lt;/strong&gt;: A new dataset with fields including &lt;code&gt;AlertID&lt;/code&gt;, &lt;code&gt;CompletedAt&lt;/code&gt;, &lt;code&gt;Destination&lt;/code&gt;, &lt;code&gt;FinalDisposition&lt;/code&gt;, &lt;code&gt;Folder&lt;/code&gt;, &lt;code&gt;From&lt;/code&gt;, &lt;code&gt;FromName&lt;/code&gt;, &lt;code&gt;MessageID&lt;/code&gt;, &lt;code&gt;MessageTimestamp&lt;/code&gt;, &lt;code&gt;MicrosoftTenantID&lt;/code&gt;, &lt;code&gt;Operation&lt;/code&gt;, &lt;code&gt;PostfixID&lt;/code&gt;, &lt;code&gt;Reasons&lt;/code&gt;, &lt;code&gt;Recipient&lt;/code&gt;, &lt;code&gt;RequestedAt&lt;/code&gt;, &lt;code&gt;RequestedBy&lt;/code&gt;, &lt;code&gt;RequestedDisposition&lt;/code&gt;, &lt;code&gt;Status&lt;/code&gt;, &lt;code&gt;Subject&lt;/code&gt;, &lt;code&gt;Success&lt;/code&gt;, and &lt;code&gt;To&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Magic Network Monitoring Flow Logs&lt;/strong&gt;: A new dataset with fields including &lt;code&gt;AWSVPCFlowJSON&lt;/code&gt;, &lt;code&gt;Bits&lt;/code&gt;, &lt;code&gt;DestinationAS&lt;/code&gt;, &lt;code&gt;DestinationAddress&lt;/code&gt;, &lt;code&gt;DestinationPort&lt;/code&gt;, &lt;code&gt;DeviceID&lt;/code&gt;, &lt;code&gt;EgressBits&lt;/code&gt;, &lt;code&gt;EgressPackets&lt;/code&gt;, &lt;code&gt;Ethertype&lt;/code&gt;, &lt;code&gt;FlowProtocol&lt;/code&gt;, &lt;code&gt;FlowTimestamp&lt;/code&gt;, &lt;code&gt;NumFlows&lt;/code&gt;, &lt;code&gt;PacketID&lt;/code&gt;, &lt;code&gt;Packets&lt;/code&gt;, &lt;code&gt;Protocol&lt;/code&gt;, &lt;code&gt;RuleIDs&lt;/code&gt;, &lt;code&gt;SampleRate&lt;/code&gt;, &lt;code&gt;SampleRateType&lt;/code&gt;, &lt;code&gt;SamplerAddress&lt;/code&gt;, &lt;code&gt;SourceAS&lt;/code&gt;, &lt;code&gt;SourceAddress&lt;/code&gt;, &lt;code&gt;SourcePort&lt;/code&gt;, &lt;code&gt;TcpFlags&lt;/code&gt;, and &lt;code&gt;Timestamp&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;div tabindex=&quot;-1&quot; class=&quot;heading-wrapper level-h4&quot;&gt;&lt;h4 id=&quot;updated-fields-in-existing-datasets&quot;&gt;Updated fields in existing datasets&lt;/h4&gt;&lt;a class=&quot;anchor-link&quot; href=&quot;#updated-fields-in-existing-datasets&quot;&gt;&lt;span aria-hidden=&quot;true&quot; class=&quot;anchor-icon&quot;&gt;&lt;svg width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 24 24&quot;&gt;&lt;path fill=&quot;currentcolor&quot; d=&quot;m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Firewall events&lt;/strong&gt; (added): &lt;code&gt;AISecurityInjectionScore&lt;/code&gt;, &lt;code&gt;AISecurityPIICategories&lt;/code&gt;, &lt;code&gt;AISecurityTokenCount&lt;/code&gt;, and &lt;code&gt;AISecurityUnsafeTopicCategories&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;HTTP requests&lt;/strong&gt; (added): &lt;code&gt;AISecurityInjectionScore&lt;/code&gt;, &lt;code&gt;AISecurityPIICategories&lt;/code&gt;, &lt;code&gt;AISecurityTokenCount&lt;/code&gt;, &lt;code&gt;AISecurityUnsafeTopicCategories&lt;/code&gt;, and &lt;code&gt;Subrequests&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For the complete field definitions for each dataset, refer to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/&quot;&gt;Logpush datasets&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Wed, 13 May 2026 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>Logs - Logpush subrequest merging for HTTP requests</title><link>https://developers.cloudflare.com/changelog/post/2026-04-21-logpush-subrequests-merging/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-04-21-logpush-subrequests-merging/</guid><description>&lt;p&gt;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, subrequest data is embedded as a nested array field on the parent log record instead.&lt;/p&gt;
&lt;div tabindex=&quot;-1&quot; class=&quot;heading-wrapper level-h4&quot;&gt;&lt;h4 id=&quot;whats-new&quot;&gt;What&apos;s new&lt;/h4&gt;&lt;a class=&quot;anchor-link&quot; href=&quot;#whats-new&quot;&gt;&lt;span aria-hidden=&quot;true&quot; class=&quot;anchor-icon&quot;&gt;&lt;svg width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 24 24&quot;&gt;&lt;path fill=&quot;currentcolor&quot; d=&quot;m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;New subrequest_merging field on Logpush jobs — Set &quot;merge_subrequests&quot;: true when creating or updating an http_requests Logpush job to enable the feature.&lt;/li&gt;
&lt;li&gt;New Subrequests log field — When subrequest merging is enabled, a Subrequests field (&lt;code&gt;array\&amp;lt;object\&amp;gt;&lt;/code&gt;) is added to each parent request log record. Each element in the array contains the standard http_requests fields for that subrequest.&lt;/li&gt;
&lt;/ul&gt;
&lt;div tabindex=&quot;-1&quot; class=&quot;heading-wrapper level-h4&quot;&gt;&lt;h4 id=&quot;limitations&quot;&gt;Limitations&lt;/h4&gt;&lt;a class=&quot;anchor-link&quot; href=&quot;#limitations&quot;&gt;&lt;span aria-hidden=&quot;true&quot; class=&quot;anchor-icon&quot;&gt;&lt;svg width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 24 24&quot;&gt;&lt;path fill=&quot;currentcolor&quot; d=&quot;m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;Applies to the http_requests (zone-scoped) dataset only.&lt;/li&gt;
&lt;li&gt;A maximum of 50 subrequests are merged per parent request. Subrequests beyond this limit are passed through unmodified as individual log entries.&lt;/li&gt;
&lt;li&gt;Subrequests must complete within 5 minutes of the visitor request. Subrequests that exceed this window are passed through unmodified.&lt;/li&gt;
&lt;li&gt;Subrequests that do not qualify appear as separate log entries — no data is lost.&lt;/li&gt;
&lt;li&gt;Subrequest merging is being gradually rolled out and is not yet available on all zones. Contact your account team for concerns or to ensure it is enabled for your zone.&lt;/li&gt;
&lt;li&gt;For more information, refer to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/subrequests/&quot;&gt;Subrequests&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;</description><pubDate>Tue, 21 Apr 2026 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>Logs, Basin Pipelines - Cloudflare Pipelines as a Logpush destination</title><link>https://developers.cloudflare.com/changelog/post/2026-04-20-pipelines-logpush-destination/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-04-20-pipelines-logpush-destination/</guid><description>&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;With this release, you can now send your logs directly to &lt;a href=&quot;https://developers.cloudflare.com/basin-pipelines/&quot;&gt;Pipelines&lt;/a&gt; to ingest, transform, and store your logs in &lt;a href=&quot;https://developers.cloudflare.com/r2/&quot;&gt;R2&lt;/a&gt; as Parquet files or Apache Iceberg tables managed by &lt;a href=&quot;https://developers.cloudflare.com/basin-catalog/&quot;&gt;R2 Data Catalog&lt;/a&gt;. This makes the data footprint more compact and more efficient at querying your logs instantly with &lt;a href=&quot;https://developers.cloudflare.com/basin-sql/&quot;&gt;R2 SQL&lt;/a&gt; or any other query engine that supports Apache Iceberg or Parquet.&lt;/p&gt;
&lt;div tabindex=&quot;-1&quot; class=&quot;heading-wrapper level-h4&quot;&gt;&lt;h4 id=&quot;transform-logs-before-storage&quot;&gt;Transform logs before storage&lt;/h4&gt;&lt;a class=&quot;anchor-link&quot; href=&quot;#transform-logs-before-storage&quot;&gt;&lt;span aria-hidden=&quot;true&quot; class=&quot;anchor-icon&quot;&gt;&lt;svg width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 24 24&quot;&gt;&lt;path fill=&quot;currentcolor&quot; d=&quot;m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;
&lt;p&gt;Pipelines SQL runs on each log record in-flight, so you can reshape your data before it is written. For example, you can drop noisy fields, redact sensitive values, or derive new columns:&lt;/p&gt;
&lt;figure class=&quot;nb-code-figure&quot; data-nb-lang=&quot;sql&quot;&gt;&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark nb-shiki-c6xiwz&quot; tabindex=&quot;0&quot; data-language=&quot;sql&quot; data-nb-lang=&quot;sql&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;nb-shiki-1itgoe&quot;&gt;INSERT INTO&lt;/span&gt;&lt;span class=&quot;nb-shiki-140thh&quot;&gt; http_logs_sink&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;nb-shiki-1itgoe&quot;&gt;SELECT&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;nb-shiki-140thh&quot;&gt;  ClientIP,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;nb-shiki-140thh&quot;&gt;  EdgeResponseStatus,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;nb-shiki-140thh&quot;&gt;  to_timestamp_micros(EdgeStartTimestamp) &lt;/span&gt;&lt;span class=&quot;nb-shiki-1itgoe&quot;&gt;AS&lt;/span&gt;&lt;span class=&quot;nb-shiki-140thh&quot;&gt; event_time,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;nb-shiki-dzsirb&quot;&gt;  upper&lt;/span&gt;&lt;span class=&quot;nb-shiki-140thh&quot;&gt;(ClientRequestMethod) &lt;/span&gt;&lt;span class=&quot;nb-shiki-1itgoe&quot;&gt;AS&lt;/span&gt;&lt;span class=&quot;nb-shiki-140thh&quot;&gt; method,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;nb-shiki-140thh&quot;&gt;  sha256(ClientIP) &lt;/span&gt;&lt;span class=&quot;nb-shiki-1itgoe&quot;&gt;AS&lt;/span&gt;&lt;span class=&quot;nb-shiki-140thh&quot;&gt; hashed_ip&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;nb-shiki-1itgoe&quot;&gt;FROM&lt;/span&gt;&lt;span class=&quot;nb-shiki-140thh&quot;&gt; http_logs_stream&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;nb-shiki-1itgoe&quot;&gt;WHERE&lt;/span&gt;&lt;span class=&quot;nb-shiki-140thh&quot;&gt; EdgeResponseStatus &lt;/span&gt;&lt;span class=&quot;nb-shiki-1itgoe&quot;&gt;&amp;gt;=&lt;/span&gt;&lt;span class=&quot;nb-shiki-dzsirb&quot;&gt; 400&lt;/span&gt;&lt;span class=&quot;nb-shiki-140thh&quot;&gt;;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;
&lt;p&gt;Pipelines SQL supports string functions, regex, hashing, JSON extraction, timestamp conversion, conditional expressions, and more. For the full list, refer to the &lt;a href=&quot;https://developers.cloudflare.com/basin-pipelines/sql-reference/&quot;&gt;Pipelines SQL reference&lt;/a&gt;.&lt;/p&gt;
&lt;div tabindex=&quot;-1&quot; class=&quot;heading-wrapper level-h4&quot;&gt;&lt;h4 id=&quot;get-started&quot;&gt;Get started&lt;/h4&gt;&lt;a class=&quot;anchor-link&quot; href=&quot;#get-started&quot;&gt;&lt;span aria-hidden=&quot;true&quot; class=&quot;anchor-icon&quot;&gt;&lt;svg width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 24 24&quot;&gt;&lt;path fill=&quot;currentcolor&quot; d=&quot;m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;
&lt;p&gt;To configure Pipelines as a Logpush destination, refer to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/enable-destinations/pipelines/&quot;&gt;Enable Cloudflare Pipelines&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Mon, 20 Apr 2026 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category><category>Basin Pipelines</category></item><item><title>Logs - New TenantID and Firewall for AI fields in Logpush datasets</title><link>https://developers.cloudflare.com/changelog/post/2026-04-15-logpush-new-fields/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-04-15-logpush-new-fields/</guid><description>&lt;p&gt;Cloudflare has added new fields to multiple &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/&quot;&gt;Logpush datasets&lt;/a&gt;:&lt;/p&gt;
&lt;div tabindex=&quot;-1&quot; class=&quot;heading-wrapper level-h4&quot;&gt;&lt;h4 id=&quot;tenantid-field&quot;&gt;TenantID field&lt;/h4&gt;&lt;a class=&quot;anchor-link&quot; href=&quot;#tenantid-field&quot;&gt;&lt;span aria-hidden=&quot;true&quot; class=&quot;anchor-icon&quot;&gt;&lt;svg width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 24 24&quot;&gt;&lt;path fill=&quot;currentcolor&quot; d=&quot;m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;
&lt;p&gt;The following Gateway and Zero Trust datasets now include a &lt;code&gt;TenantID&lt;/code&gt; field:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/gateway_dns/#tenantid&quot;&gt;Gateway DNS&lt;/a&gt;&lt;/strong&gt;: Identifies the tenant ID of the DNS request, if it exists.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/gateway_http/#tenantid&quot;&gt;Gateway HTTP&lt;/a&gt;&lt;/strong&gt;: Identifies the tenant ID of the HTTP request, if it exists.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/gateway_network/#tenantid&quot;&gt;Gateway Network&lt;/a&gt;&lt;/strong&gt;: Identifies the tenant ID of the network session, if it exists.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/zero_trust_network_sessions/#tenantid&quot;&gt;Zero Trust Network Sessions&lt;/a&gt;&lt;/strong&gt;: Identifies the tenant ID of the network session, if it exists.&lt;/li&gt;
&lt;/ul&gt;
&lt;div tabindex=&quot;-1&quot; class=&quot;heading-wrapper level-h4&quot;&gt;&lt;h4 id=&quot;firewall-for-ai-fields&quot;&gt;Firewall for AI fields&lt;/h4&gt;&lt;a class=&quot;anchor-link&quot; href=&quot;#firewall-for-ai-fields&quot;&gt;&lt;span aria-hidden=&quot;true&quot; class=&quot;anchor-icon&quot;&gt;&lt;svg width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 24 24&quot;&gt;&lt;path fill=&quot;currentcolor&quot; d=&quot;m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;
&lt;p&gt;The following datasets now include &lt;a href=&quot;https://developers.cloudflare.com/api-shield/security/volumetric-abuse-detection/#firewall-for-ai&quot;&gt;Firewall for AI&lt;/a&gt; fields:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/zone/firewall_events/&quot;&gt;Firewall Events&lt;/a&gt;&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;FirewallForAIInjectionScore&lt;/code&gt;: The score indicating the likelihood of a prompt injection attack in the request.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;FirewallForAIPIICategories&lt;/code&gt;: List of PII categories detected in the request.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;FirewallForAITokenCount&lt;/code&gt;: The number of tokens in the request.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;FirewallForAIUnsafeTopicCategories&lt;/code&gt;: List of unsafe topic categories detected in the request.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/zone/http_requests/&quot;&gt;HTTP Requests&lt;/a&gt;&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;FirewallForAIInjectionScore&lt;/code&gt;: The score indicating the likelihood of a prompt injection attack in the request.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;FirewallForAIPIICategories&lt;/code&gt;: List of PII categories detected in the request.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;FirewallForAITokenCount&lt;/code&gt;: The number of tokens in the request.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;FirewallForAIUnsafeTopicCategories&lt;/code&gt;: List of unsafe topic categories detected in the request.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For the complete field definitions for each dataset, refer to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/&quot;&gt;Logpush datasets&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Wed, 15 Apr 2026 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>logpush, Logs - Logpush to BigQuery — Cloudflare dashboard support</title><link>https://developers.cloudflare.com/changelog/post/2026-04-14-bigquery-dashboard-support/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-04-14-bigquery-dashboard-support/</guid><description>&lt;p&gt;You can now configure Logpush jobs to Google BigQuery directly from the Cloudflare dashboard, in addition to the existing API-based setup.&lt;/p&gt;
&lt;p&gt;Previously, setting up a BigQuery Logpush destination required using the Logpush API. Now you can create and manage BigQuery Logpush jobs from the &lt;strong&gt;Logpush&lt;/strong&gt; page in the Cloudflare dashboard by selecting &lt;strong&gt;Google BigQuery&lt;/strong&gt; as the destination and entering your Google Cloud project ID, dataset ID, table ID, and service account credentials.&lt;/p&gt;
&lt;p&gt;For more information, refer to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/enable-destinations/bigquery/&quot;&gt;Enable Logpush to Google BigQuery&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Tue, 14 Apr 2026 00:00:00 GMT</pubDate><product>logpush</product><category>logpush</category><category>Logs</category></item><item><title>Logs - New ResponseTimeMs field in Gateway DNS Logpush dataset</title><link>https://developers.cloudflare.com/changelog/post/2026-04-06-gateway-dns-response-time-ms/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-04-06-gateway-dns-response-time-ms/</guid><description>&lt;p&gt;Cloudflare has added a new field to the &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/gateway_dns/#responsetimems&quot;&gt;Gateway DNS&lt;/a&gt; Logpush dataset:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;ResponseTimeMs&lt;/strong&gt;: Total response time of the DNS request in milliseconds.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For the complete field definitions, refer to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/gateway_dns/&quot;&gt;Gateway DNS dataset&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Mon, 06 Apr 2026 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>Logs - BigQuery as Logpush destination</title><link>https://developers.cloudflare.com/changelog/post/2026-04-02-bigquery-destination/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-04-02-bigquery-destination/</guid><description>&lt;p&gt;Cloudflare Logpush now supports &lt;strong&gt;BigQuery&lt;/strong&gt; as a native destination.&lt;/p&gt;
&lt;p&gt;Logs from Cloudflare can be sent to &lt;a href=&quot;https://cloud.google.com/bigquery&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Google Cloud BigQuery&lt;span class=&quot;external-link&quot;&gt; ↗︎&lt;/span&gt;&lt;/a&gt; via &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/&quot;&gt;Logpush&lt;/a&gt;. The destination can be configured through the Logpush UI in the Cloudflare dashboard or by using the &lt;a href=&quot;https://developers.cloudflare.com/api/resources/logpush/subresources/jobs/&quot;&gt;Logpush API&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;For more information, refer to the &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/enable-destinations/bigquery/&quot;&gt;Destination Configuration&lt;/a&gt; documentation.&lt;/p&gt;</description><pubDate>Thu, 02 Apr 2026 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>logpush, Logs - Logpush — More granular timestamps</title><link>https://developers.cloudflare.com/changelog/post/2026-03-25-logpush-granular-timestamps/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-03-25-logpush-granular-timestamps/</guid><description>&lt;p&gt;Logpush now supports higher-precision timestamp formats for log output. You can configure jobs to output timestamps at millisecond or nanosecond precision. This is available in both the Logpush UI in the Cloudflare dashboard and the &lt;a href=&quot;https://developers.cloudflare.com/api/resources/logpush/subresources/jobs/&quot;&gt;Logpush API&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;To use the new formats, set &lt;code&gt;timestamp_format&lt;/code&gt; in your Logpush job&apos;s &lt;code&gt;output_options&lt;/code&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;rfc3339ms&lt;/code&gt; — &lt;code&gt;2024-02-17T23:52:01.123Z&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;rfc3339ns&lt;/code&gt; — &lt;code&gt;2024-02-17T23:52:01.123456789Z&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Default timestamp formats apply unless explicitly set. The dashboard defaults to &lt;code&gt;rfc3339&lt;/code&gt; and the API defaults to &lt;code&gt;unixnano&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;For more information, refer to the &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/log-output-options/&quot;&gt;Log output options&lt;/a&gt; documentation.&lt;/p&gt;</description><pubDate>Wed, 25 Mar 2026 00:00:00 GMT</pubDate><product>logpush</product><category>logpush</category><category>Logs</category></item><item><title>Logs - New MCP Portal Logs dataset and new fields across multiple Logpush datasets in Cloudflare Logs</title><link>https://developers.cloudflare.com/changelog/post/2026-03-09-log-fields-updated/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2026-03-09-log-fields-updated/</guid><description>&lt;p&gt;Cloudflare has added new fields across multiple &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/&quot;&gt;Logpush datasets&lt;/a&gt;:&lt;/p&gt;
&lt;div tabindex=&quot;-1&quot; class=&quot;heading-wrapper level-h4&quot;&gt;&lt;h4 id=&quot;new-dataset&quot;&gt;New dataset&lt;/h4&gt;&lt;a class=&quot;anchor-link&quot; href=&quot;#new-dataset&quot;&gt;&lt;span aria-hidden=&quot;true&quot; class=&quot;anchor-icon&quot;&gt;&lt;svg width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 24 24&quot;&gt;&lt;path fill=&quot;currentcolor&quot; d=&quot;m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;MCP Portal Logs&lt;/strong&gt;: A new dataset with fields including &lt;code&gt;ClientCountry&lt;/code&gt;, &lt;code&gt;ClientIP&lt;/code&gt;, &lt;code&gt;ColoCode&lt;/code&gt;, &lt;code&gt;Datetime&lt;/code&gt;, &lt;code&gt;Error&lt;/code&gt;, &lt;code&gt;Method&lt;/code&gt;, &lt;code&gt;PortalAUD&lt;/code&gt;, &lt;code&gt;PortalID&lt;/code&gt;, &lt;code&gt;PromptGetName&lt;/code&gt;, &lt;code&gt;ResourceReadURI&lt;/code&gt;, &lt;code&gt;ServerAUD&lt;/code&gt;, &lt;code&gt;ServerID&lt;/code&gt;, &lt;code&gt;ServerResponseDurationMs&lt;/code&gt;, &lt;code&gt;ServerURL&lt;/code&gt;, &lt;code&gt;SessionID&lt;/code&gt;, &lt;code&gt;Success&lt;/code&gt;, &lt;code&gt;ToolCallName&lt;/code&gt;, &lt;code&gt;UserEmail&lt;/code&gt;, and &lt;code&gt;UserID&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;div tabindex=&quot;-1&quot; class=&quot;heading-wrapper level-h4&quot;&gt;&lt;h4 id=&quot;new-fields-in-existing-datasets&quot;&gt;New fields in existing datasets&lt;/h4&gt;&lt;a class=&quot;anchor-link&quot; href=&quot;#new-fields-in-existing-datasets&quot;&gt;&lt;span aria-hidden=&quot;true&quot; class=&quot;anchor-icon&quot;&gt;&lt;svg width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 24 24&quot;&gt;&lt;path fill=&quot;currentcolor&quot; d=&quot;m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;DEX Application Tests&lt;/strong&gt;: &lt;code&gt;HTTPRedirectEndMs&lt;/code&gt;, &lt;code&gt;HTTPRedirectStartMs&lt;/code&gt;, &lt;code&gt;HTTPResponseBody&lt;/code&gt;, and &lt;code&gt;HTTPResponseHeaders&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;DEX Device State Events&lt;/strong&gt;: &lt;code&gt;ExperimentalExtra&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Firewall Events&lt;/strong&gt;: &lt;code&gt;FraudUserID&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Gateway HTTP&lt;/strong&gt;: &lt;code&gt;AppControlInfo&lt;/code&gt; and &lt;code&gt;ApplicationStatuses&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Gateway DNS&lt;/strong&gt;: &lt;code&gt;InternalDNSDurationMs&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;HTTP Requests&lt;/strong&gt;: &lt;code&gt;FraudEmailRisk&lt;/code&gt;, &lt;code&gt;FraudUserID&lt;/code&gt;, and &lt;code&gt;PayPerCrawlStatus&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Network Analytics Logs&lt;/strong&gt;: &lt;code&gt;DNSQueryName&lt;/code&gt;, &lt;code&gt;DNSQueryType&lt;/code&gt;, and &lt;code&gt;PFPCustomTag&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;WARP Toggle Changes&lt;/strong&gt;: &lt;code&gt;UserEmail&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;WARP Config Changes&lt;/strong&gt;: &lt;code&gt;UserEmail&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Zero Trust Network Session Logs&lt;/strong&gt;: &lt;code&gt;SNI&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For the complete field definitions for each dataset, refer to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/&quot;&gt;Logpush datasets&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Mon, 09 Mar 2026 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>Logs - SentinelOne as Logpush destination</title><link>https://developers.cloudflare.com/changelog/post/2025-12-11-sentinelone-destination/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2025-12-11-sentinelone-destination/</guid><description>&lt;p&gt;Cloudflare Logpush now supports &lt;strong&gt;SentinelOne&lt;/strong&gt; as a native destination.&lt;/p&gt;
&lt;p&gt;Logs from Cloudflare can be sent to &lt;a href=&quot;https://www.sentinelone.com/&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;SentinelOne AI SIEM&lt;span class=&quot;external-link&quot;&gt; ↗︎&lt;/span&gt;&lt;/a&gt; via &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/&quot;&gt;Logpush&lt;/a&gt;. The destination can be configured through the Logpush UI in the Cloudflare dashboard or by using the &lt;a href=&quot;https://developers.cloudflare.com/api/resources/logpush/subresources/jobs/&quot;&gt;Logpush API&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;For more information, refer to the &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/enable-destinations/sentinelone/&quot;&gt;Destination Configuration&lt;/a&gt; documentation.&lt;/p&gt;</description><pubDate>Thu, 11 Dec 2025 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>Logs - Logpush Health Dashboards</title><link>https://developers.cloudflare.com/changelog/post/2025-11-11-health-dashboards/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2025-11-11-health-dashboards/</guid><description>&lt;p&gt;We’re excited to introduce &lt;strong&gt;Logpush Health Dashboards&lt;/strong&gt;, giving customers real-time visibility into the status, reliability, and performance of their &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/&quot;&gt;Logpush&lt;/a&gt; jobs. Health dashboards make it easier to detect delivery issues, monitor job stability, and track performance across destinations. The dashboards are divided into two sections:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Upload Health&lt;/strong&gt;: See how much data was successfully uploaded, where drops occurred, and how your jobs are performing overall. This includes data completeness, success rate, and upload volume.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Upload Reliability&lt;/strong&gt; – Diagnose issues impacting stability, retries, or latency, and monitor key metrics such as retry counts, upload duration, and destination availability.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;img src=&quot;https://developers.cloudflare.com/cdn-cgi/image/onerror=redirect,width=1333,height=334,format=webp/_astro/Health-Dashboard.CP0mV0IW.gif&quot; alt=&quot;Health Dashboard&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; width=&quot;1333&quot; height=&quot;334&quot;&gt;
&lt;p&gt;Health Dashboards can be accessed from the Logpush page in the Cloudflare dashboard at the account or zone level, under the Health tab. For more details, refer to our &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-health&quot;&gt;&lt;strong&gt;Logpush Health Dashboards&lt;/strong&gt;&lt;/a&gt; documentation, which includes a comprehensive troubleshooting guide to help interpret and resolve common issues.&lt;/p&gt;</description><pubDate>Tue, 11 Nov 2025 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>Logs - Logpush Permission Update for Zero Trust Datasets</title><link>https://developers.cloudflare.com/changelog/post/2025-11-05-logpush-permissions-update/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2025-11-05-logpush-permissions-update/</guid><description>&lt;p&gt;&lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/permissions/&quot;&gt;Permissions&lt;/a&gt; for managing Logpush jobs related to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/&quot;&gt;Zero Trust datasets&lt;/a&gt; (Access, Gateway, and DEX) have been updated to improve data security and enforce appropriate access controls.&lt;/p&gt;
&lt;p&gt;To view, create, update, or delete Logpush jobs for Zero Trust datasets, users must now have both of the following permissions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Logs Edit&lt;/li&gt;
&lt;li&gt;Zero Trust: PII Read&lt;/li&gt;
&lt;/ul&gt;
&lt;aside role=&quot;note&quot; aria-label=&quot;Note&quot; class=&quot;aside-card flex items-start gap-3 rounded-lg px-4 py-3 my-4&quot; style=&quot;--_c: var(--nb-info); --_t: var(--nb-info-muted);&quot; data-astro-cid-znle5jil&gt;&lt;span class=&quot;flex h-[1.375em] shrink-0 items-center&quot; aria-hidden=&quot;true&quot; data-astro-cid-znle5jil&gt;&lt;svg width=&quot;1em&quot; height=&quot;1em&quot; viewBox=&quot;0 0 256 256&quot; class=&quot;h-[1em] w-[1em]&quot; data-astro-cid-znle5jil=&quot;true&quot; data-icon=&quot;ph:info&quot;&gt;&lt;path fill=&quot;currentColor&quot; d=&quot;M128 24a104 104 0 1 0 104 104A104.11 104.11 0 0 0 128 24m0 192a88 88 0 1 1 88-88a88.1 88.1 0 0 1-88 88m16-40a8 8 0 0 1-8 8a16 16 0 0 1-16-16v-40a8 8 0 0 1 0-16a16 16 0 0 1 16 16v40a8 8 0 0 1 8 8m-32-92a12 12 0 1 1 12 12a12 12 0 0 1-12-12&quot;/&gt;&lt;/svg&gt;&lt;/span&gt;&lt;div class=&quot;flex min-w-0 flex-1 flex-col gap-0.5&quot; data-astro-cid-znle5jil&gt;&lt;p class=&quot;m-0 text-base leading-snug font-semibold&quot; data-astro-cid-znle5jil&gt;Note&lt;/p&gt;&lt;div class=&quot;aside-card-body text-sm leading-normal&quot; data-astro-cid-znle5jil&gt;&lt;p&gt;Update your UI, API or Terraform configurations to include the new permissions. Requests to Zero Trust datasets will fail due to insufficient access without the additional permission.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/aside&gt;</description><pubDate>Wed, 05 Nov 2025 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>Logs - Azure Sentinel Connector</title><link>https://developers.cloudflare.com/changelog/post/2025-10-27-Sentinel-connector/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2025-10-27-Sentinel-connector/</guid><description>&lt;p&gt;Logpush now supports integration with &lt;a href=&quot;https://www.microsoft.com/en-us/security/business/siem-and-xdr/microsoft-sentinel&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Microsoft Sentinel&lt;span class=&quot;external-link&quot;&gt; ↗︎&lt;/span&gt;&lt;/a&gt;.The new Azure Sentinel Connector built on Microsoft’s Codeless Connector Framework (CCF), is now available. This solution replaces the previous Azure Functions-based connector, offering significant improvements in security, data control, and ease of use for customers. Logpush customers can send logs to Azure Blob Storage and configure this new Sentinel Connector to ingest those logs directly into Microsoft Sentinel.&lt;/p&gt;
&lt;p&gt;This upgrade significantly streamlines log ingestion, improves security, and provides greater control:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Simplified Implementation: Easier for engineering teams to set up and maintain.&lt;/li&gt;
&lt;li&gt;Cost Control: New support for Data Collection Rules (DCRs) allows you to filter and transform logs at ingestion time, offering potential cost savings.&lt;/li&gt;
&lt;li&gt;Enhanced Security: CCF provides a higher level of security compared to the older Azure Functions connector.&lt;/li&gt;
&lt;li&gt;Data Lake Integration: Includes native integration with Data Lake.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Find the new solution &lt;a href=&quot;https://marketplace.microsoft.com/en-us/product/azure-application/cloudflare.azure-sentinel-solution-cloudflare-ccf?tab=Overview&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;here&lt;span class=&quot;external-link&quot;&gt; ↗︎&lt;/span&gt;&lt;/a&gt; and refer to the &lt;a href=&quot;https://developers.cloudflare.com/analytics/analytics-integrations/sentinel/#supported-logs:~:text=WorkBook%20fields,-Analytic%20rules&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Cloudflare&apos;s developer documentation&lt;span class=&quot;external-link&quot;&gt; ↗︎&lt;/span&gt;&lt;/a&gt;for more information on the connector, including setup steps, supported logs and Microsoft&apos;s resources.&lt;/p&gt;</description><pubDate>Mon, 27 Oct 2025 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>Logs - Dedicated Egress IP for Logpush</title><link>https://developers.cloudflare.com/changelog/post/2025-08-22-dedicated-egress-ip-logpush/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2025-08-22-dedicated-egress-ip-logpush/</guid><description>&lt;p&gt;Cloudflare Logpush can now deliver logs from using fixed, dedicated egress IPs. By routing Logpush traffic through a Cloudflare zone enabled with &lt;a href=&quot;https://developers.cloudflare.com/smart-shield/configuration/dedicated-egress-ips/&quot;&gt;Aegis IP&lt;/a&gt;, your log destination only needs to allow Aegis IPs making setup more secure.&lt;/p&gt;
&lt;p&gt;Highlights:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed egress IPs ensure your destination only accepts traffic from known addresses.&lt;/li&gt;
&lt;li&gt;Works with any supported Logpush destination.&lt;/li&gt;
&lt;li&gt;Recommended to use a dedicated zone as a proxy for easier management.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;To get started, work with your Cloudflare account team to provision Aegis IPs, then configure your Logpush job to deliver logs through the proxy zone. For full setup instructions, refer to the &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/enable-destinations/egress-ip/&quot;&gt;Logpush documentation&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Fri, 22 Aug 2025 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>Logs - IBM Cloud Logs as Logpush destination</title><link>https://developers.cloudflare.com/changelog/post/2025-08-13-ibm-cloud-logs-destination/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2025-08-13-ibm-cloud-logs-destination/</guid><description>&lt;p&gt;Cloudflare Logpush now supports IBM Cloud Logs as a native destination.&lt;/p&gt;
&lt;p&gt;Logs from Cloudflare can be sent to &lt;a href=&quot;https://www.ibm.com/products/cloud-logs&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;IBM Cloud Logs&lt;span class=&quot;external-link&quot;&gt; ↗︎&lt;/span&gt;&lt;/a&gt; via &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/&quot;&gt;Logpush&lt;/a&gt;. The setup can be done through the Logpush UI in the Cloudflare Dashboard or by using the &lt;a href=&quot;https://developers.cloudflare.com/api/resources/logpush/subresources/jobs/&quot;&gt;Logpush API&lt;/a&gt;. The integration requires IBM Cloud Logs HTTP Source Address and an IBM API Key. The feature also allows for filtering events and selecting specific log fields.&lt;/p&gt;
&lt;p&gt;For more information, refer to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/enable-destinations/ibm-cloud-logs/&quot;&gt;Destination Configuration&lt;/a&gt; documentation.&lt;/p&gt;</description><pubDate>Wed, 13 Aug 2025 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>Logs - Custom fields raw and transformed values support</title><link>https://developers.cloudflare.com/changelog/post/2025-04-18-custom-fields-raw-transformed-values/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2025-04-18-custom-fields-raw-transformed-values/</guid><description>&lt;p&gt;Custom Fields now support logging both &lt;strong&gt;raw and transformed values&lt;/strong&gt; for request and response headers in the HTTP requests dataset.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;By default:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Request headers are logged as raw values&lt;/li&gt;
&lt;li&gt;Response headers are logged as transformed values&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These defaults can be overridden to suit your logging needs.&lt;/p&gt;
&lt;aside role=&quot;note&quot; aria-label=&quot;Note&quot; class=&quot;aside-card flex items-start gap-3 rounded-lg px-4 py-3 my-4&quot; style=&quot;--_c: var(--nb-info); --_t: var(--nb-info-muted);&quot; data-astro-cid-znle5jil&gt;&lt;span class=&quot;flex h-[1.375em] shrink-0 items-center&quot; aria-hidden=&quot;true&quot; data-astro-cid-znle5jil&gt;&lt;svg width=&quot;1em&quot; height=&quot;1em&quot; viewBox=&quot;0 0 256 256&quot; class=&quot;h-[1em] w-[1em]&quot; data-astro-cid-znle5jil=&quot;true&quot; data-icon=&quot;ph:info&quot;&gt;&lt;path fill=&quot;currentColor&quot; d=&quot;M128 24a104 104 0 1 0 104 104A104.11 104.11 0 0 0 128 24m0 192a88 88 0 1 1 88-88a88.1 88.1 0 0 1-88 88m16-40a8 8 0 0 1-8 8a16 16 0 0 1-16-16v-40a8 8 0 0 1 0-16a16 16 0 0 1 16 16v40a8 8 0 0 1 8 8m-32-92a12 12 0 1 1 12 12a12 12 0 0 1-12-12&quot;/&gt;&lt;/svg&gt;&lt;/span&gt;&lt;div class=&quot;flex min-w-0 flex-1 flex-col gap-0.5&quot; data-astro-cid-znle5jil&gt;&lt;p class=&quot;m-0 text-base leading-snug font-semibold&quot; data-astro-cid-znle5jil&gt;Note&lt;/p&gt;&lt;div class=&quot;aside-card-body text-sm leading-normal&quot; data-astro-cid-znle5jil&gt;&lt;p&gt;Transformed and raw values for request and response headers are available &lt;strong&gt;only via the API&lt;/strong&gt; and cannot be set through the UI.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/aside&gt;
&lt;p&gt;For more information refer to &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/custom-fields/&quot;&gt;Custom fields&lt;/a&gt; documentation&lt;/p&gt;</description><pubDate>Fri, 18 Apr 2025 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>Logs - One-click Logpush Setup with R2 Object Storage</title><link>https://developers.cloudflare.com/changelog/post/2025-03-06-oneclick-logpush/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2025-03-06-oneclick-logpush/</guid><description>&lt;p&gt;We’ve streamlined the &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/&quot;&gt;Logpush&lt;/a&gt; setup process by integrating R2 bucket creation directly into the Logpush workflow!&lt;/p&gt;
&lt;p&gt;Now, you no longer need to navigate multiple pages to manually create an R2 bucket or copy credentials. With this update, you can seamlessly &lt;strong&gt;configure a Logpush job to R2 in just one click&lt;/strong&gt;, reducing friction and making setup faster and easier.&lt;/p&gt;
&lt;p&gt;This enhancement makes it easier for customers to adopt Logpush and R2.&lt;/p&gt;
&lt;p&gt;For more details refer to our &lt;a href=&quot;https://developers.cloudflare.com/logs/logpush/logpush-job/enable-destinations/r2/&quot;&gt;Logs&lt;/a&gt; documentation.&lt;/p&gt;</description><pubDate>Thu, 06 Mar 2025 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item><item><title>Logs - New fields added to Gateway-related datasets in Cloudflare Logs</title><link>https://developers.cloudflare.com/changelog/post/2024-10-08-new-gateway-fields/</link><guid isPermaLink="true">https://developers.cloudflare.com/changelog/post/2024-10-08-new-gateway-fields/</guid><description>&lt;p&gt;Cloudflare has introduced new fields to two Gateway-related datasets in Cloudflare Logs:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Gateway HTTP&lt;/strong&gt;: &lt;code&gt;ApplicationIDs&lt;/code&gt;, &lt;code&gt;ApplicationNames&lt;/code&gt;, &lt;code&gt;CategoryIDs&lt;/code&gt;, &lt;code&gt;CategoryNames&lt;/code&gt;, &lt;code&gt;DestinationIPContinentCode&lt;/code&gt;, &lt;code&gt;DestinationIPCountryCode&lt;/code&gt;, &lt;code&gt;ProxyEndpoint&lt;/code&gt;, &lt;code&gt;SourceIPContinentCode&lt;/code&gt;, &lt;code&gt;SourceIPCountryCode&lt;/code&gt;, &lt;code&gt;VirtualNetworkID&lt;/code&gt;, and &lt;code&gt;VirtualNetworkName&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Gateway Network&lt;/strong&gt;: &lt;code&gt;ApplicationIDs&lt;/code&gt;, &lt;code&gt;ApplicationNames&lt;/code&gt;, &lt;code&gt;DestinationIPContinentCode&lt;/code&gt;, &lt;code&gt;DestinationIPCountryCode&lt;/code&gt;, &lt;code&gt;ProxyEndpoint&lt;/code&gt;, &lt;code&gt;SourceIPContinentCode&lt;/code&gt;, &lt;code&gt;SourceIPCountryCode&lt;/code&gt;, &lt;code&gt;TransportProtocol&lt;/code&gt;, &lt;code&gt;VirtualNetworkID&lt;/code&gt;, and &lt;code&gt;VirtualNetworkName&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;</description><pubDate>Tue, 08 Oct 2024 00:00:00 GMT</pubDate><product>Logs</product><category>Logs</category></item></channel></rss>