Skip to content

[Logpush] Updated "Enable Datadog" page with Limitations section, outlining Datadog's hard limits. #25580

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from
Closed

[Logpush] Updated "Enable Datadog" page with Limitations section, outlining Datadog's hard limits. #25580

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
fbb0d87
Update datadog.mdx
reichbc Oct 1, 2025
4894e7a
Refined formatting.
reichbc Oct 1, 2025
374f195
Updated Changelog.
reichbc Oct 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions src/content/docs/logs/changelog/logs.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,10 +11,14 @@ 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 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`.
- **Gateway Network**: `ApplicationIDs`, `ApplicationNames`, `DestinationIPContinentCode`, `DestinationIPCountryCode`, `ProxyEndpoint`, `SourceIPContinentCode`, `SourceIPCountryCode`, `TransportProtocol`, `VirtualNetworkID`, and `VirtualNetworkName`.
17 changes: 17 additions & 0 deletions src/content/docs/logs/logpush/logpush-job/enable-destinations/datadog.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,23 @@ 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" />
Expand Down
Loading