Skip to main content

Out Of Memory Killed Container

Home > Select Project > Container > Out Of Memory Killed Container

Through the Out Of Memory Killed Container menu, you can quickly search for containers where Out Of Memory (OOM) occurred, and you can check changes in the memory usage (abrupt or gradual) at each time. This allows an objective determination of the eligible number of PODs and the memory thresholds.


Example of OOM occurrence

Out Of Memory occurs when the container's memory usage exceeds its limit, or the node on which the container is running encounters an out-of-memory condition. If the container exits with the code 137, it indicates that SIGKILL has been received by Out Of Memory.

Basic screen guide

Out Of Memory Killed Container

  • You can select a time zone to view by clicking the time selector at the upper left. You can search for up to 2 days.

  • It provides the OOM killed containers in the list format. For more information, see the following guide.

OOM killed container information

The columns in Out Of Memory Killed Container are as follows:

OomKilledAtTime stamp where Out Of Memory Killed occurred
nameContainer name
podNameName of the Pod to which the container belongs
containerIdContainer ID
createdTime stamp generated by the container
commandContainer's execution command
imageNameContainer's image name
onodeNameNode name on which the container is running
stateContainer status
memLimitContainer's memory limit size
namespaceName of the namespace to which the container's Pod belongs
memory_workingsetActual memory in use, excluding the memory disabled in the container