- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
If you decide to run your Agent on your host to monitor kubernetes, in order to start collecting your Kubernetes metrics you should:
Download the Kube-State manifests folder.
Apply them to your Kubernetes cluster:
kubectl apply -f <NAME_OF_THE_KUBE_STATE_MANIFESTS_FOLDER>
Once done, the Kubernetes State integration automatically collects kube-state metrics.
Since Agent v6, Kubernetes DNS integration works automatically with the Autodiscovery.
Note: these metrics are unavailable for Azure Kubernetes Service (AKS).
Available for Agent >6.0
There are two ways to collect logs from containers running in Kubernetes:
Datadog recommends using the Kubernetes log files approach when you are either not using Docker, or are using more than 10 containers per pod.
Datadog also recommends that you take advantage of DaemonSets to automatically deploy the Datadog Agent on all your nodes.
Otherwise, to manually enable log collection from one specific node, add the following parameters in the datadog.yaml
:
logs_enabled: true
listeners:
- name: kubelet
config_providers:
- name: kubelet
polling: true
logs_config:
container_collect_all: true
Use Autodiscovery with Pod Annotations to configure log collection to add multiline processing rules, or to customize the source
and service
attributes.
To get a better idea of how (or why) to integrate your Kubernetes service, see the related series of Datadog blog posts.