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
--------------------------------------------- x 100 = Memory utilization (%)
Memory limit of pod
Example:
WSS memory usage = 150MiB
Memory limit set for that pod = 256MiB
Memory utilization by percentage = 150 / 256 x 100 = 58.5%
For CPU utilization, the calculation works as follows:
CPU usage
-------------------- x 100 = CPU utilization (%)
CPU limit of pod
Example:
CPU usage = 200 millicores
CPU limit of that pod = 400 millicores
CPU utilization in percentage = 200 / 400 x 100 = 50%
Related Articles
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, ...
No data for service and process in Windows server monitor
If you see "No Data" for process and service metrics (such as CPU or memory usage of monitored services) in the Site24x7 Windows server monitor user interface, follow the troubleshooting steps below. Run PowerShell Commands Open PowerShell as ...
How do I monitor an Oracle database hosted in a Docker container in the same machine?
To monitor your Oracle Database hosted in a Docker container, follow these steps: Log in to Site24x7 and install the Site24x7 Linux monitoring agent. Execute the following command in your terminal and enter your Oracle Database instance's username ...
Difference between website monitoring and REST API monitoring
Website monitoring allows you to monitor your websites and web applications to ensure that they are up and running. Website monitor verifies the availability of specified, addressable, standard HTTP and HTTPS URLs from over 100+ global locations and ...
Response time in Website monitoring
In website monitoring, response time is calculated as the total time taken to resolve the DNS, complete the TCP hand-shake, negotiate an SSL handshake (for HTTPS) and download the full HTML output from the server. However, it does not include getting ...