Why it matters
It usually picks the biggest process, which is often your database or app server. From the outside it looks like a random crash; the only trace is a line in the kernel log. Repeated OOM kills mean the server needs more memory, swap, or limits on what is running.
How to check it on Linux
Find OOM kills in the kernel log:
sudo journalctl -k | grep -i "out of memory"What Opservo does about it
Opservo counts OOM kills since boot, reads them from the kernel log and takes health-score points for each one. The Opservo Health Standard
OOM killer, answered
What is the OOM killer?+
The OOM (out-of-memory) killer is the part of the Linux kernel that kills a process when memory runs out, so the whole server does not freeze.
How do I check the OOM killer on Linux?+
Find OOM kills in the kernel log: sudo journalctl -k | grep -i "out of memory"
How does Opservo handle the OOM killer?+
Opservo counts OOM kills since boot, reads them from the kernel log and takes health-score points for each one.