...
- Cluster collector that runs on some worker node (depending on where Kubernetes decides to schedule it)
- Two types of node collectors run on each worker node:
- container metrics collector (collects CPU and memory metrics on containers running on the respective nodes)
- machine sections collector (runs the Checkmk agent on the respective nodes)
The docker images that are run inside these pods as containers can be found on Dockerhub: https://hub.docker.com/r/checkmk/kubernetes-collector
...
- Previous: shows the logs of the previously failed container. This is useful if the current container has been running successfully for the time being and does not submit any error logs.
- Container: select the container if there is more than one container inside a pod. This is the case for the container metrics collector: it runs cadvisor (a 3rd party open source tool) and a container-metrics-collector. Usually, we are interested in the latter.
In addition to the above steps, you can ask the client to set the log level to debug. This is done in the yaml manifests or helm charts used to deploy the Kubernetes components. Once the modifications have been made, the components must be deployed to the cluster again.
...