Page Comparison

...

Getting Started

Background information regarding this subject is available on our:

• Official documentation
• YouTube Video

General data

...

For diagnostic purposes,  please send us a dump of the support diagnostics so we can

...

take a closer look at what might be happening.

Detailed instructions on how to create such a dump are available in our official guide:

...

https://docs.checkmk.com/latest/en/support_diagnostics.html

...

• Local files
• OMD Config
• Checkmk Overview
• Checkmk Configuration files
• Performance Graphs of Checkmk Server
• Global Settings

• What kind of Kubernetes distro + version are you using?

  Code Block
  language bash theme RDark
  uname -a cat /etc/os-release

The debug of the special agent:
Please run the special agent on the command line. You will find here some information on how to get the correct command: Special Agents, and here you will find all the debug options for Debugging the Kubernetes - k8s special agent.

• 
  

• Some additional outputs, as described

in 

• in Debug Kubernetes Cluster Components

  Code Block
  language bash theme RDark
  kubectl get pods -A kubectl get nodes -A kubectl version -o json

  
  

• Please run the special agent on the command line

  • Command for Special Agents 

  • Debugging the Kubernetes - k8s special agent

Debug Kubernetes Cluster Components

A couple of pods are deployed to the Kubernetes cluster for monitoring:

• 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.

...

kubectl get pods
kubectl get nodes
kubectl version -o json

Related articles

...