Why is No Data shown for the Pod metrics?

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 below: 


This happens because the Site24x7 Kubernetes agent cannot collect CPU limits or requests or memory limits or requests if the resource configuration is not set for the Pod in its respective deployment file, as shown below:


 


You will be able to see the metrics in the Site24x7 web client if the resource configuration for the Pod is set in its respective deployment file, as shown below:  




Now, the output will be:




How do we calculate CPU Utilization and Memory Utilization?

 

CPU Utilization is calculated as below:

  CPU Utilization = (CPU Usage/CPU Limit) * 100

 

Memory Utilization is calculated as below:

              Memory Utilization (%) = (Memory Usage/Memory Limit) * 100

 

Since the CPU and Memory Utilization metrics depend on their respective configuration data limit, they will be shown as No Data.

 

However, CPU Usage (millicores) and Memory Usage (mebibytes) will be shown irrespective of the resource configuration.

    • 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 ...
    • Data retention period for APM metrics

      The table below explains the data retention period for APM metrics data stored by Site24x7. Data type Retention period Traces 7 days Raw data or other metrics 30 days Reports 5 years Related Articles: Data retention for logs Data retention in Real ...
    • 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 ...
    • 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 ...
    • Data retention in Real User Monitoring (RUM).

      The following table explains the data retention period of real user monitoring data that are being stored by Site24x7.  S.No Data type Retention period 1 JS errors One week 2 Filterable performance and user sessions One month 3 Performance metrics ...