When monitoring Kubernetes metrics, what statistic is NOT typically tracked?

When monitoring Kubernetes metrics, the statistic that is not typically tracked is the total API requests. While Kubernetes does have an extensive list of metrics that are essential for observing the health and performance of the cluster, such as memory and CPU usage, tracking the total number of API requests is not directly related to the resource metrics of the Kubernetes nodes, pods, or containers themselves.

Monitoring CPU and memory metrics is fundamental as it provides insights into resource utilization and efficiency, which are crucial for managing workloads and ensuring that applications run smoothly. Available CPU resources are also a critical metric to understand how much computational capacity is available for scheduling new workloads or scaling existing ones.

Total API requests, on the other hand, typically involve tracking interactions with the Kubernetes API server and may be more relevant in the context of API rate limiting or monitoring application-level metrics rather than resource utilization. Therefore, while it is important for overall application monitoring, it does not fall under the primary metrics associated with Kubernetes resource monitoring.