Kubernetes Not Added

Possible reasons why Kubernetes monitor is not added to Site24x7

  • Check if the option Auto discover applications on the server is set to Yes in Settings (Admin > Server Monitor > Settings). Alternatively, you can also click on Discover Applications in the monitor's Summary page (hover on hamburger icon beside display name > Discover Applications).
  • Ensure proxy is configured correctly. Read our help documentation.
  • Check if the device key has been entered correctly in the YAML file.
  • Only one Site24x7 Linux agent can be installed in a node. If you already have an agent installed in the server, installing it again via Kubernetes will throw an error and not install in the pod. To resolve this issue, uninstall the existing node agent and install as the DaemonSet agent
  • Make sure you have sufficient licensing. Read more about Kubernetes licensing.
  • If the issue persists, access the agent pod and share logs to support@site24x7.com for troubleshooting.

      • Related Articles

      • 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 ...
      • How to migrate Kubernetes monitors from one Site24x7 account to another

        Use case An existing Site24x7 user has Kubernetes monitoring in a Site24x7 account and plans to migrate his Kubernetes monitors to a different account. The historic data and the current display name of the Kubernetes monitors will not be migrated. ...
      • APM Insight monitor not getting added to my account

        The most probable reason will be a wrong license key used while adding the agent. Check if you have added the agent in the application with the correct license key. If you have used the correct license key and still the monitor is not getting added, ...
      • 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 ...
      • 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 ...