Datadog Agent Source

문서 > Observability Pipelines > Sources > Datadog Agent Source

이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

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

로그를 수집하고 Datadog Log Management로 라우팅하기 위해 Datadog Agent가 이미 설치되어 있습니다. Datadog Agent가 설정되어 있지 않은 경우 자세한 내용은 Datadog Agent 설명서를 참조하세요.

다음 정보를 사용할 수 있습니다.

활성화된 원격 구성이 포함된 Datadog API 키.
Datadog Site URL. (예: 사이트 US1의 경우 datadoghq.com)

Set up the source in the pipeline UI

이 단계에서는 설정할 수 있는 항목이 없습니다.

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.

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.