A few nodes or pods are not discovered for monitoring. Why?

A few nodes or pods are not discovered for monitoring. Why?

Check for the below cases if applicable.

Case 1: License inadequacy
Check if you have adequate licensing. If not, upgrade your license.

Case 2: Taint configurations
If a few nodes are not discovered for monitoring, it might be because the node has a taint configuration. If so, the Site24x7 agent DaemonSet will not be able to spawn the pods on that node.
To add the node for monitoring, you need to configure the toleration to enable the Site24x7 agent to spawn on that node.
An example for the taints configured to a sample node is shown below:

Configuring tolerations

1. To configure tolerations for the Site24x7 agent DaemonSet for the above taints, open the downloaded site24x7-agent.yaml file and add the tolerations under the spec section as shown below:

2. After configuring the above tolerations in the Site24x7 agent YAML file, execute the below command:

kubectl apply -f site24x7-agent.yaml

You have successfully configured the tolerations for the taints.

 

Customers also searched this KB for the below problem statements:

There is a mismatch in the number of nodes in the Cluster dashboard and the Monitors List View page.

I am not able to see all the pod logs.

A few pods are missing for monitoring.

Some nodes are not added for monitoring.


    • Related Articles

    • Licensing for Kubernetes monitoring

      The main Kubernetes cluster is considered one basic monitor. For the other components, the licensing is done as follows: Component Licensing Nodes 1 monitor consumes two basic licenses Pods 5 monitors consume one basic license Containers 5 monitors ...

    • How do I monitor specific resource types like Pods, Containers, and Deployments?

      To monitor specific resource types of Kubernetes like Pods, Containers, and Deployments: Log in to your Site24x7 account. Go to Admin > Inventory > Configuration Rules. Click Add Rule. Enter a proper Display Name and Description. Define the Criteria ...

    • How does Site24x7 Kubernetes monitor calculate the memory and CPU utilization for pods?

      Site24x7 Kubernetes Monitor uses the kubelet API and kube-state-metrics API to collect the metrics related to memory and CPU utilization. For memory utilization, the calculation works as follows: Working set size (WSS) memory usage ...

    • Unable to see my Kubernetes resources on the monitor list page

      This case is applicable if your Kubernetes resource monitors are listed in the Kubernetes Monitor List View page instead of Monitor Status listing (Home) page. Site24x7 will not list the Kubernetes resources along with the other monitors on the home ...

    • Why is No Data shown for the Pod metrics?

      In your Site24x7 web client (Server > Kubernetes > Pods > select the Pod monitor > click Performance), you might get No Data for metrics such as CPU Limit and Requests, Memory Limit and Requests, CPU Utilization, and Memory Utilization (%) as shown ...