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:

• The Datadog Agent address, including the port.
  • The Observability Pipelines Worker listens to this socket address to receive logs from the Datadog Agent.
• A Datadog API key with Remote Configuration enabled.
• Your Datadog Site URL. For example, datadoghq.com for the site US1.

Set up the source in the pipeline UI

There are no settings to configure in this step.

Connect the Datadog Agent to the Observability Pipelines Worker

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

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

<OPW_HOST> is the IP/URL of the host (or load balancer) associated with the Observability Pipelines Worker. For CloudFormation installs, the LoadBalancerDNS CloudFormation output has the correct URL to use. For Kubernetes installs, the internal DNS record of the Observability Pipelines Worker service can be used. For example: datadog-observability-pipelines-worker.default.svc.cluster.local.

At this point, your observability data should be going to the Worker, processed by the pipeline, and delivered to Datadog.