Kubernetes Observability

​

Overview

GermainUX provides real-time monitoring, analytics, alerting, and automation for Kubernetes environments. Monitor the health, availability, and performance of Kubernetes infrastructure—from clusters and nodes to pods and containers—and quickly identify conditions affecting the applications and services running within them. What GermainUX can help teams detect:

​

Collected Metrics

The Kubernetes monitor collects the KPIs below. Which KPIs are collected depends on the monitor’s Collect cluster status and Collect cluster metrics settings. In the Name column, <dataSource> is the monitor’s data source name. “Configured namespace” means the monitor’s Namespace setting (default: default). Namespace scope: KPIs for pods, containers, workloads (deployments, stateful sets, daemon sets) and unschedulable pods only cover the configured namespace. Node-level and cluster-level KPIs cover all namespaces.

​

Cluster status

Collected only when Collect cluster status is enabled.

​

Cluster metrics: nodes

Collected only when Collect cluster metrics is enabled. Usage values come from the Kubernetes Metrics API.

​

Cluster metrics: cluster

Collected only when Collect cluster metrics is enabled.

​

Cluster metrics: containers

Collected only when Collect cluster metrics is enabled.

​

Availability & Health Monitoring

Continuously monitor the operational health of your Kubernetes environment. GermainUX can monitor Kubernetes components such as: It can also monitor the status and health of: This provides teams with real-time visibility into infrastructure conditions that may affect application availability or performance.

​

Container Monitoring

Monitor the status and resource utilization of individual containers running within Kubernetes pods. GermainUX can provide visibility into:

​

Container Status

Monitor container status, including readiness and liveness, to quickly identify containers that are unavailable or unhealthy.

​

Container Restarts

Track container restart counts to identify instability, recurring failures, or abnormal behavior.

​

Container CPU

Monitor CPU utilization to detect excessive resource consumption, capacity constraints, and potential performance bottlenecks.

​

Container Memory

Monitor memory utilization to identify excessive consumption and potential memory-related performance issues.

​

Pod Monitoring

Monitor the health and status of pods throughout the Kubernetes environment. GermainUX can monitor information such as: This helps teams identify pods that are unhealthy, unavailable, or contributing to application performance issues.

​

Node Monitoring

Monitor Kubernetes nodes to understand infrastructure health and resource utilization. GermainUX can track:

​

Node CPU

Monitor CPU utilization across Kubernetes nodes to identify resource constraints and unusual consumption.

​

Node Memory

Monitor node memory utilization to identify capacity issues and memory pressure that may affect workloads. Combining node, pod, and container monitoring provides visibility from the infrastructure layer down to individual workloads.

​

Kubernetes Configuration & Control Monitoring

GermainUX can monitor additional Kubernetes information that provides context around the state and behavior of the environment. This includes:

​

Control Flags

Monitor Kubernetes control information associated with operations such as:

​

Display Hints

Collect contextual information exposed by Kubernetes for containers, pods, and nodes to provide additional insight during analysis and troubleshooting.

​

Detect Kubernetes Issues in Real Time

GermainUX can continuously analyze Kubernetes telemetry to identify conditions that require attention. For example: This helps teams move from manually reviewing infrastructure metrics to proactively identifying the conditions that require action.

​

Analytics, Dashboards & Reports

Kubernetes monitoring data can be analyzed through GermainUX real-time dashboards and automated reports. Examples include:

Show all 9

• Node CPU utilization
• Node memory utilization
• Infrastructure health and performance

Dashboards, KPIs, and reports are customizable to match the architecture and operational requirements of each Kubernetes environment.

​

Alerts & SLA Monitoring

Configure alerts and SLA thresholds for Kubernetes conditions such as:

Show all 9

• Node CPU above threshold
• Node memory above threshold
• Kubernetes server health issues

Alert conditions, thresholds, time windows, recipients, and escalation logic can be customized according to operational requirements.

​

Automation

GermainUX can trigger automated actions when specific Kubernetes conditions are detected. For example: Depending on the use case, automation can include:

Show all 9

• Scheduled actions
• Custom operational workflows
• Remediation actions where appropriate

This allows Kubernetes monitoring to become part of a broader operational workflow rather than simply generating additional alerts.

​

Correlate Kubernetes with Applications & Services

Kubernetes infrastructure does not operate in isolation. GermainUX can combine Kubernetes monitoring with telemetry from applications, APIs, databases, Java services, operating systems, and other technologies monitored by GermainUX. This provides broader visibility across the technology stack: Teams can use this context to determine whether an application performance or availability issue originates in the application itself or in the Kubernetes infrastructure supporting it.

​

Configuration

Kubernetes monitoring is performed through the GermainUX Engine. Deploy and configure a GermainUX Engine with access to the Kubernetes environment, then select the components, KPIs, thresholds, alerts, and automation appropriate for your environment. See Deploy Monitoring for Kubernetes for detailed deployment and configuration instructions. GermainUX itself can also be deployed within a Kubernetes container.

​

Additional Resources

​

Get Help

The content of this document is proprietary to GERMAIN SOFTWARE.