Datadog Agent Source

This product is not supported for your selected Datadog site. ().

Use Observability Pipelines’ Datadog Agent source to receive logs from the Datadog Agent. Select and set up this source when you set up a pipeline.

Prerequisites

You already have the Datadog Agent installed to collect and route your logs to Datadog Log Management. If you do not have Datadog Agents set up, see the Datadog Agent documentation for more information.

You have the following information available:

Set up the source in the pipeline UI

Select and set up this source when you set up a pipeline. The information below is for the source settings in the pipeline UI.

There are no settings to configure in this step.

Set the environment variables

  • Datadog Agent address:
    • The Observability Pipelines Worker listens to this socket address to receive logs from the Datadog Agent.
    • Stored in the environment variableDD_OP_SOURCE_DATADOG_AGENT_ADDRESS.

Connect the Datadog Agent to the Observability Pipelines Worker

Use the Agent configuration file or the Agent Helm chart values file to connect the Datadog Agent to the Observability Pipelines Worker.

Note: If your Agent is running in a Docker container, you must exclude Observability Pipelines logs using the DD_CONTAINER_EXCLUDE_LOGS environment variable. For Helm, use datadog.containerExcludeLogs. This prevents duplicate logs, as the Worker also sends its own logs directly to Datadog. See Docker Log Collection or Setting environment variables for Helm for more information.

    To send Datadog Agent logs to the Observability Pipelines Worker, update your Agent configuration file with the following:

    observability_pipelines_worker:
  logs:
    enabled: true
    url: "http://<OPW_HOST>:8282"

    <OPW_HOST> is the host IP address or the load balancer URL associated with the Observability Pipelines Worker.

    For CloudFormation installs, use the LoadBalancerDNS CloudFormation output for the URL.

    For Kubernetes installs, you can use the internal DNS record of the Observability Pipelines Worker service. For example: opw-observability-pipelines-worker.default.svc.cluster.local.

    After you restart the Agent, your observability data should be going to the Worker, processed by the pipeline, and delivered to Datadog.

    To send Datadog Agent logs to the Observability Pipelines Worker, update your Datadog Helm chart datadog-values.yaml with the following environment variables. See Agent Environment Variables for more information.

    datadog:
  env:
    - name: DD_OBSERVABILITY_PIPELINES_WORKER_LOGS_ENABLED
      value: true
    - name: DD_OBSERVABILITY_PIPELINES_WORKER_LOGS_URL
      value: "http://<OPW_HOST>:8282"

    <OPW_HOST> is the IP/URL of the host (or load balancer) associated with the Observability Pipelines Worker.

    For Kubernetes installs, you can use the internal DNS record of the Observability Pipelines Worker service. For example: opw-observability-pipelines-worker.default.svc.cluster.local.

    PREVIEWING: may/restructure-op-docs