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

    • Add Node.js agent in Kubernetes via InitContainers (using prebuilt agent image)

      To integrate the APM Insight Node.js agent into your Kubernetes applications using InitContainers, follow the steps given below: Step 1: Create an empty volume that will be used to copy the agent files during the initContainers process. Example: ...

    • Troubleshooting false positive alerts in monitoring

      Problem False positive alerts are being generated. Possible cause The monitoring system is down in some locations. The Website monitor might be configured for one location, such as Seattle, but may appear down when accessed from another location, ...

    • Why are my resources not being discovered?

      When you cannot view the newly added Azure resources in your Azure monitor, you can check if Auto-discovery is disabled. If it is enabled, new resources will be added during auto-discovery. Manual triggering If your resource is not discovered, you ...

    • Unable to add SQL insight monitor

      If the SQL Insight monitor is not getting added even after entering your credentials, try these troubleshooting steps: Ensure that the Auto-discover applications feature is enabled. If not, you will need to trigger discovery using the Discover ...

    • How does Site24x7 always ensure the availability of its location agents during monitoring?

      Site24x7 uses a preferred location recheck logic in the back-end to ensure the availability of all monitoring locations. This logic is only applied when you've disabled the option "Restrict monitoring within selected locations" in the Add or Edit ...