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.
Check if Taints are applied using the below command:
kubectl describe node <node-name>

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

    • Unable to use the latest features and the new metrics in Kubernetes

      You need to upgrade your Site24x7 Kubernetes monitoring agent to derive the new metrics and use the latest features. To do this, follow the steps below: Uninstall the existing Kubernetes monitoring agent to prevent any configuration conflicts. ...

    • Licensing for Kubernetes monitoring

      The licensing for the Kubernetes monitors is as follows: Component Licensing Cluster One cluster monitor consumes one basic monitor license Nodes One node monitor consumes two host licenses* *The first 10 containers on each node are free. After that, ...

    • How to enable Kubernetes monitoring on clusters that have arm-based nodes

      If you would like to add a Kubernetes monitor for your clusters that have arm-based nodes, ensure that you have followed the steps below: Download the latest site24x7-agent.yaml file from the Site24x7 web console. Replace the image name ...

    • Licensing for Kubernetes monitoring (old)

      This article contains the licensing model for the customers who signed up before August 2024. Check out this article for more information on the new licensing pattern. Note that the new licensing model applies to users who signed up after August ...

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