Kubernetes KPIs

​

Kubernetes Metrics Overview: Pod, Container, and Node Statuses

​

Overview

GermainUX collects Kubernetes KPIs to monitor the health, availability, resource utilization, and stability of clusters, nodes, pods, and containers. These KPIs can be used for real-time monitoring, dashboards, SLA tracking, alerting, analysis, and automation. They also provide supporting technology evidence when investigating user-experience, application, or business-process issues in the Analysis Dashboard.

​

Kubernetes KPIs

​

Pod Status

Kubernetes monitors the status of each Kubernetes Pod. One metric is generated for each Pod, allowing GermainUX to identify Pods that are not operating in their expected state. The Data Source name identifies both the GermainUX Kubernetes Data Source and the Pod: <GermainUX Data Source>:<Pod Name> Example: d710a3b4:lyjvms-sts-3 Use this KPI to:

​

Container Status

Kubernetes monitors the status of individual containers running within Kubernetes Pods. One metric is generated for each Container. The Data Source name identifies the Kubernetes Data Source, Pod, and Container: <GermainUX Data Source>:<Pod Name>:<Container Name> Example: d710a3b4:lyjvms-sts-2:apache-pocjvms Use this KPI to identify containers that are unavailable or not operating in their expected state.

​

Container Restart Count

Kubernetes monitors container restarts within the Kubernetes cluster. The Data Source name identifies the monitored Kubernetes cluster. Example: d710a3b4 Use restart count to identify container instability and investigate whether repeated restarts are associated with application availability, errors, or performance issues.

​

Node CPU Usage

Kubernetes CPU Usage monitors CPU utilization for each Kubernetes Node. One metric is generated for each Node. The Node is identified using its metadata.name. Example: 10.230.92.57 Use this KPI to identify sustained or abnormal CPU utilization that may affect Pods, Containers, services, or applications running on the Node.

​

Node Memory Usage

Kubernetes Memory Usage monitors memory utilization for each Kubernetes Node. One metric is generated for each Node and identified using its metadata.name. Use this KPI to identify memory pressure or abnormal memory utilization that may affect workloads running on the Node.

​

Container CPU Usage

Kubernetes CPU Usage monitors CPU utilization at the individual Container level. One metric is generated for each Container and identified using the Container’s metadata.name. Use this KPI to:

​

Container Memory Usage

Kubernetes Memory Usage monitors memory utilization at the individual Container level. One metric is generated for each Container and identified using the Container’s metadata.name. Use this KPI to:

​

Analyze Kubernetes Health

Kubernetes KPIs can be monitored in GermainUX dashboards and analyzed alongside application, service, user-experience, and business KPIs. For example: Application Performance Degradation
→ Technology Health
→ Kubernetes Node CPU Usage
→ Affected Node
→ Pods & Containers
→ Related KPIs
→ Analysis
→ Likely Root Cause Or: Service Failure
→ Kubernetes
→ Affected Container
→ Pod
→ Container Restart Count
→ Related Application Errors
→ Analysis

​

Technology Health

Kubernetes KPIs can be surfaced in the Technology Health view of the Operational Dashboard to provide real-time visibility into the infrastructure supporting monitored applications. This can help identify whether an application or user issue is associated with:

​

Alerts & Automation

Kubernetes KPIs can be associated with SLAs, alerts, Rules, and Automation to detect and respond to abnormal conditions. For example: Container Status Changes
→ Detect condition
→ Analyze affected application/service
→ Alert appropriate team
→ Create or update ticket
→ Continue monitoring
→ Validate recovery The available actions depend on the GermainUX configuration and permissions.

​

Related Documentation

​

Additional Resources

​

Get Help

The content of this document is proprietary to GERMAIN SOFTWARE LLC.