Enable Datadog

import { Render, TabItem, Tabs, APIRequest } from "~/components";

Cloudflare Logpush supports pushing logs directly to Datadog via the Cloudflare dashboard or via API.

Manage via the Cloudflare dashboard

4. In Select a destination, choose Datadog.

5. Enter or select the following destination information:

   • Datadog URL Endpoint, which can be either one below. You can find the difference at Datadog API reference.

• http-intake.logs.datadoghq.com/v1/input

• http-intake.logs.datadoghq.com/api/v2/logs

• Datadog API Key, can be retrieved by following these steps.

• Service, Hostname, Datadog ddsource field, and ddtags fields can be set as URL parameters. For more information, refer to the Logs section in Datadog's documentation. While these parameters are optional, they can be useful for indexing or processing logs. Note that the values of these parameters may contain special characters, which should be URL encoded.

When you are done entering the destination details, select Continue.

6. Select the dataset to push to the storage service.

7. In the next step, you need to configure your logpush job:

   • Enter the Job name.
   • Under If logs match, you can select the events to include and/or remove from your logs. Refer to Filters for more information. Not all datasets have this option available.
   • In Send the following fields, you can choose to either push all logs to your storage destination or selectively choose which logs you want to push.

8. In Advanced Options, you can:

   • Choose the format of timestamp fields in your logs (RFC3339 (default), Unix, or UnixNano).
   • Select a sampling rate for your logs or push a randomly-sampled percentage of logs.
   • Enable redaction for CVE-2021-44228. This option will replace every occurrence of ${ with x{.

9. Select Submit once you are done configuring your logpush job.

Manage via API

To set up a Datadog Logpush job:

1. Create a job with the appropriate endpoint URL and authentication parameters.
2. Enable the job to begin pushing logs.

:::note[Note]

Unlike configuring Logpush jobs for AWS S3, GCS, or Azure, there is no ownership challenge when configuring Logpush to Datadog.

:::

1. Create a job

To create a job, make a POST request to the Logpush jobs endpoint with the following fields:

• name (optional) - Use your domain name as the job name.

• destination_conf - A log destination consisting of an endpoint URL, authorization header, and zero or more optional parameters that Datadog supports in the string format below.

  • <DATADOG_ENDPOINT_URL>: The Datadog HTTP logs intake endpoint, which can be either one below. You can find the difference at Datadog API reference.

  https://http-intake.logs.datadoghq.com/v1/input`

  https://http-intake.logs.datadoghq.com/api/v2/logs

• <DATADOG_API_KEY>: The Datadog API token can be retrieved by following these steps. For example, 20e6d94e8c57924ad1be3c29bcaee0197d.

• ddsource: Set to cloudflare.

• service, host, ddtags: Optional parameters allowed by Datadog.

"datadog://<DATADOG_ENDPOINT_URL>?header_DD-API-KEY=<DATADOG_API_KEY>&ddsource=cloudflare&service=<SERVICE>&host=<HOST>&ddtags=<TAGS>"

• dataset - The category of logs you want to receive. Refer to Datasets for the full list of supported datasets.
• output_options (optional) - To configure fields, sample rate, and timestamp format, refer to Log Output Options.

Example request using cURL:

<APIRequest path="/zones/{zone_id}/logpush/jobs" method="POST" json={{ name: "<DOMAIN_NAME>", destination_conf: "datadog://<DATADOG_ENDPOINT_URL>?header_DD-API-KEY=<DATADOG_API_KEY>&ddsource=cloudflare&service=&host=&ddtags=", output_options: { field_names: [ "ClientIP", "ClientRequestHost", "ClientRequestMethod", "ClientRequestURI", "EdgeEndTimestamp", "EdgeResponseBytes", "EdgeResponseStatus", "EdgeStartTimestamp", "RayID", ], timestamp_format: "rfc3339", }, dataset: "http_requests", enabled: true, }} />

Response:

{
  "errors": [],
  "messages": [],
  "result": {
    "id": <JOB_ID>,
    "dataset": "http_requests",
    "kind": "",
    "enabled": true,
    "name": "<DOMAIN_NAME>",
    "output_options": {
      "field_names": ["ClientIP", "ClientRequestHost", "ClientRequestMethod", "ClientRequestURI", "EdgeEndTimestamp", "EdgeResponseBytes", "EdgeResponseStatus" ,"EdgeStartTimestamp", "RayID"],
      "timestamp_format": "rfc3339"
    },
    "destination_conf": "datadog://<DATADOG_ENDPOINT_URL>?header_DD-API-KEY=<DATADOG_API_KEY>",
    "last_complete": null,
    "last_error": null,
    "error_message": null
  },
  "success": true
}

Refer to Manage Logpush with cURL to update a job (including enabling and disabling).

:::note[Note]

The Datadog destination is exclusive to new jobs and might not be backward compatible with older jobs. Create new jobs if you expect to send your logs directly to Datadog instead of modifying already existing ones. If you try to modify an existing job for another destination to push logs to Datadog, you may observe errors. :::

:::note[Note]

To analyze and visualize Cloudflare metrics using the Cloudflare Integration tile for Datadog, follow the steps in the Datadog Analytics integration page. :::

Limitations

Note the following Logpush sending limitations, as described in the Datadog documentation.

Send your logs to your Datadog platform over HTTP. Limits per HTTP request are the following:

• Maximum content size per payload (uncompressed): 5 MB
• Maximum size for a single log: 1 MB
• Maximum array size if sending multiple logs in an array: 1,000 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. :::