The top lines about %Cpu, Memory, and Swap show values for the whole zCX instance, not  for the specific container that you are in. In contrast, the process list shows the processes of  the container that you are currently working in. Note:  You are already within the  ibm_zcx_zos_cli  container when you log in to zCX. The  ibm_zcx_zos_cli  container provides the shell functions for zCX. The  top  command updates its display periodically. To stop the display, press  control-C . In the ssh CLI where you are logged on, you can enter the  top  command to get a first view of  the zCX instance. You can then enter the  top  command for the different containers by using  the  docker exec  command as shown in Example 7-29. Most containers should be able to run  the command. There might be special containers for which the command is not implemented. If your checks in the  top  display do not give any hints about a problem situation, you can enter  a similar command for the Docker containers that are running. This is the command  docker  stats , which shows output that is similar to what you see in Example 30. Eventually, you can identify a misbehaving process on this layer. Give special attention to the  systems memory, and also swap usage as to the %CPU usage on the instance level. And of  course, you must monitor the %CPU and %MEM values of the processes within the different  containers. Checking Docker stats Example 30 Docker stats output CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS 52869f058a54 grafana 0.01% 20.93MiB / 1.675GiB 1.22% 4.34MB / 4.35MB 67.3MB / 200MB 17 6134d99615c6 prometheus 0.71% 23.45MiB / 1.675GiB 1.37% 2.44MB / 1.15MB 5.98MB / 8.19kB 16 2475f664e9aa cadvisor 9.79% 59.66MiB / 1.675GiB 3.48% 98.4MB / 1.71GB 104MB / 84MB 20 ddabf91531ac nodeexporter 0.00% 3.492MiB / 1.675GiB 0.20% 1.01kB / 0B 12MB / 0B 6 a0fb146c85ae registry 0.00% 5.504MiB / 1.675GiB 0.32% 3.74kB / 0B 111MB / 0B 13 cae0df807ac6 ibm_zcx_zos_cli 0.76% 27.42MiB / 1.675GiB 1.60% 534kB / 761kB 528MB / 4.1MB 19 This command shows you how the different containers behave in terms of cpu, memory,  network, and disk activity. If you see unexpected numbers, you might dive deeper into the  respective container activities. The  docker logs  command allows you to view the log of a container, as shown in Example 31  on page 160. Checking Docker logs Chapter 7. Operation  159 Example 7-29 Execute top command within a container docker exec -it registry top