- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
Supported OS
This check monitors the kernel OOM (out of memory) kill process through the Datadog Agent and the System Probe.
The OOM Kill check is included in the Datadog Agent package. It relies on an eBPF program implemented in the System Probe.
The eBPF program used by the System Probe is compiled at runtime and requires you to have access to the proper kernel headers.
On Debian-like distributions, install the kernel headers like this:
apt install -y linux-headers-$(uname -r)
On RHEL-like distributions, install the kernel headers like this:
yum install -y kernel-headers-$(uname -r)
yum install -y kernel-devel-$(uname -r)
Note: Kernel version 4.9 or later is required for the OOM Kill check to work. In addition, Windows and CentOS/RHEL versions earlier than 8 are not supported.
In the system-probe.yaml
file at the root of your Agent’s configuration directory, add the following configuration:
system_probe_config:
enable_oom_kill: true
Ensure that the oom_kill.d/conf.yaml
file is present in the conf.d/
folder at the root of your Agent’s configuration directory to start collecting your OOM Kill metrics. See the example oom_kill.d/conf.yaml for all available configuration options.
In addition to mounting system-probe.yaml
and oom_kill.d/conf.yaml
as described above, do the following configuration:
Mount the following volumes to the Agent container:
-v /sys/kernel/debug:/sys/kernel/debug
-v /lib/modules:/lib/modules
-v /usr/src:/usr/src
Add the following permission to enable BPF operations:
--privileged
From kernel version 5.8, the --privileged
parameter can be replaces by --cap-add CAP_BPF
.
Note: --privileged
mode is not supported in Docker swarm.
With the Datadog Helm chart, ensure that the datadog.systemProbe
and datadog.systemProbe.enableOOMKill
parameters are enabled in the values.yaml
file.
Set the features.oomKill.enabled
parameter in the DatadogAgent manifest:
apiVersion: datadoghq.com/v2alpha1
kind: DatadogAgent
metadata:
name: datadog
spec:
features:
oomKill:
enabled: true
Note: When using COS (Container Optimized OS), override the src
volume in the node Agent:
apiVersion: datadoghq.com/v2alpha1
kind: DatadogAgent
metadata:
name: datadog
spec:
features:
oomKill:
enabled: true
override:
nodeAgent:
volumes:
- emptyDir: {}
name: src
Run the Agent’s status subcommand and look for oom_kill
under the Checks section.
oom_kill.oom_process.count (count) | The count of processes OOM killed Shown as process |
The OOM Kill check does not include any service checks.
The OOM Kill check submits an event for each OOM Kill that includes the killed process ID and name, as well as the triggering process ID and name.
Need help? Contact Datadog support.