Updates after review

Author: angelampcosta

src/content/changelog/logs/2024-10-08-new-gateway-fields.mdx

@@ -0,0 +1,11 @@
+---
+title: New fields to Gateway-related datasets in Cloudflare Logs
+description: Cloudflare has introduced new fields to Gateway-related datasets in Cloudflare Logs.
+date: 2024-10-08
+---
+
+Cloudflare has introduced new fields to two Gateway-related datasets in Cloudflare Logs:
+
+- **Gateway HTTP**: `ApplicationIDs`, `ApplicationNames`, `CategoryIDs`, `CategoryNames`, `DestinationIPContinentCode`, `DestinationIPCountryCode`, `ProxyEndpoint`, `SourceIPContinentCode`, `SourceIPCountryCode`, `VirtualNetworkID`, and `VirtualNetworkName`.
+
+- **Gateway Network**: `ApplicationIDs`, `ApplicationNames`, `DestinationIPContinentCode`, `DestinationIPCountryCode`, `ProxyEndpoint`, `SourceIPContinentCode`, `SourceIPCountryCode`, `TransportProtocol`, `VirtualNetworkID`, and `VirtualNetworkName`.

src/content/changelog/logs/2025-10-01-datadog-hardcoded-limitations.mdx

@@ -0,0 +1,7 @@
+---
+title: Datadog hardcoded limitations
+description: Datadog hardcoded limitations and how they apply to Logpush.
+date: 2025-10-01
+---
+
+Logpush documentation has been updated for enabling Datadog, which outlines the Datadog hardcoded limitations, and how they apply to Logpush.

src/content/docs/logs/changelog/logs.mdx

@@ -11,14 +11,4 @@ import { ProductChangelog } from "~/components";
 
 <ProductChangelog product="logs" />
 
-## 2025-10-01
 
-Logpush documentation has been updated for enabling Datadog, which outlines the Datadog hardcoded limitations, and how they apply to Logpush.
-
-## 2024-10-08
-
-Cloudflare has introduced new fields two Gateway-related datasets in Cloudflare Logs:
-
-- **Gateway HTTP**: `ApplicationIDs`, `ApplicationNames`, `CategoryIDs`, `CategoryNames`, `DestinationIPContinentCode`, `DestinationIPCountryCode`, `ProxyEndpoint`, `SourceIPContinentCode`, `SourceIPCountryCode`, `VirtualNetworkID`, and `VirtualNetworkName`.
-
-- **Gateway Network**: `ApplicationIDs`, `ApplicationNames`, `DestinationIPContinentCode`, `DestinationIPCountryCode`, `ProxyEndpoint`, `SourceIPContinentCode`, `SourceIPCountryCode`, `TransportProtocol`, `VirtualNetworkID`, and `VirtualNetworkName`.

src/content/docs/logs/logpush/logpush-job/enable-destinations/datadog.mdx

@@ -12,23 +12,6 @@ import { Render, TabItem, Tabs, APIRequest } from "~/components";
 
 Cloudflare Logpush supports pushing logs directly to Datadog via the Cloudflare dashboard or via API.
 
-## Limitations
-
-Please note the following Logpush sending limitations, as described in the Datadog documentation, [here](https://docs.datadoghq.com/api/latest/logs/).
-
-> Send your logs to your Datadog platform over HTTP. **Limits per HTTP request are:**
->
-> - Maximum content size per payload (uncompressed): 5MB
-> - Maximum size for a single log: 1MB
-> - Maximum array size if sending multiple logs in an array: 1000 entries
-
-:::caution[Warning]
-
-The above limits are hardcoded defaults. It is not possible to override these limitations using the Logpush configuration values, `max_upload_records` or `max_upload_bytes`.
-
-These limitations may result in noticeable log ingestion delay within Datadog following high traffic events. Logpush will not drop unsent logs, so all logs will be uploaded to Datadog in due time.
-:::
-
 ## Manage via the Cloudflare dashboard
 
 <Render file="enable-logpush-job" product="logs" />
@@ -210,3 +193,20 @@ The Datadog destination is exclusive to new jobs and might not be backward compa
 
 To analyze and visualize Cloudflare metrics using the Cloudflare Integration tile for Datadog, follow the steps in the [Datadog Analytics integration page](/analytics/analytics-integrations/datadog/).
 :::
+
+## Limitations
+
+Note the following Logpush sending limitations, as described in the [Datadog documentation](https://docs.datadoghq.com/api/latest/logs/).
+
+Send your logs to your Datadog platform over HTTP. Limits per HTTP request are the following:
+
+- Maximum content size per payload (uncompressed): 5MB
+- Maximum size for a single log: 1MB
+- Maximum array size if sending multiple logs in an array: 1000 entries
+
+:::caution[Warning]
+
+The above limits are hardcoded defaults. It is not possible to override these limitations using the Logpush configuration values, `max_upload_records` or `max_upload_bytes`.
+
+These limitations may result in noticeable log ingestion delay within Datadog following high traffic events. Logpush will not drop unsent logs, so all logs will be uploaded to Datadog in due time.
+:::