- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
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.
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:
Site URL
. For example, datadoghq.com
for the site US1
.There are no settings to configure in this step.
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 IP/URL of the host (or load balancer) 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
.