Deploy via GermainUX Wizard
Connect cluster through wizard
Configure the Kubernetes Connection
Enter cluster connection details
Apply the Configuration
Start collecting cluster telemetry
Deploy GermainUX within Kubernetes
Run GermainUX inside cluster
Overview
Deploy Kubernetes monitoring with the GermainUX Engine to continuously monitor the health, availability, and performance of your Kubernetes environment. The easiest way to configure Kubernetes monitoring is through the GermainUX Kubernetes Wizard.Deploy via GermainUX Wizard
From GermainUX Workspace, navigate to:Left MenuSettingsWizardsKubernetes

Kubernetes Wizards - GermainUX
1. Select the Monitoring Server
Select the server that will be used by the GermainUX Engine to monitor the Kubernetes cluster. The selected server’s hostname is used to establish the connection to the Kubernetes cluster. Make sure the server:2. Select the Application
Select the Application that the Kubernetes environment should be associated with in GermainUX. If an appropriate application does not already exist, click the + icon to create one. The application label helps organize and correlate Kubernetes telemetry with other application, infrastructure, and user-experience data monitored by GermainUX.3. Configure the Kubernetes Connection
Enter the connection information for the Kubernetes cluster.Scheme
Select the protocol used to connect to the Kubernetes cluster: HTTP or HTTPS HTTPS should be used when required by your Kubernetes environment.Port
Enter the port used to connect to the Kubernetes cluster. The selected GermainUX Engine must be able to reach the Kubernetes endpoint on this port.Credentials
Provide the credentials required to connect to and monitor the Kubernetes cluster. Use credentials with the appropriate permissions for the Kubernetes resources and metrics you want GermainUX to monitor.
4. Configure the Monitoring Frequency
Define how frequently GermainUX should collect Kubernetes monitoring data. Default: 60 seconds Adjust the monitoring frequency based on your operational requirements and environment. A shorter interval provides more granular visibility, while a longer interval reduces monitoring frequency and data volume.5. Apply the Configuration
Review the Kubernetes configuration and apply it. Once configured, the GermainUX Engine begins collecting Kubernetes telemetry according to the selected monitoring frequency. Verify that Kubernetes data is being received and that the expected clusters, nodes, pods, and containers are visible in GermainUX.6. Configure Analytics & Alerts
Once monitoring is active, configure the KPIs, dashboards, reports, and alerts appropriate for your Kubernetes environment. For example, monitor and alert on:- Kubernetes component availability
- Container health
- Container restarts
- Container CPU and memory
- Pod health and availability
- Node CPU and memory
- Kubernetes server health
7. Configure Automation
GermainUX automation can be used to trigger actions when specific Kubernetes conditions are detected. For example:Detect IssueAlert TeamCreate TicketTrigger Action
Depending on the use case, actions can include notifications, ticket creation, scripts, programs, HTTP or SSH execution, and other operational workflows.
Automated remediation can also be configured for appropriate, well-understood conditions.
Deploy GermainUX within Kubernetes
GermainUX can also be configured to run within a Kubernetes container. Contact the GermainUX team if you need assistance deploying GermainUX within your Kubernetes environment.Additional Resources
Deploy
Monitoring or automation for Kubernetes
AI
Insights & Recommendations
Analytics
More Analytics Features
Automation
More Automation Features
Dashboards
Dashboards and reports overview
Reports
Automatic and scheduled reports
Get Help
Contact GermainUX Support
The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.
Can't find what you need?
Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.
The content of this document is proprietary to GERMAIN SOFTWARE.


