Monitoring
Monitoring surfaces health and resource signals so you can see whether nodes and workloads look healthy without leaving the portal. It is part of day-to-day operations on Kloude.
Open Monitoring from the products sidebar when you need a quick capacity or health check. Pair it with the resource views inside Clusters (Pods, Events, Cloud Shell) and with your own APM or log stack for application depth.
What you see in the panel
The page opens with two side tabs: Metrics for gauges and charts, and Factors for the companion view. Use the filter bar to pick a time range (for example Last 24 hours), a refresh interval (for example 5 minutes), and a view type such as Overview, then select the cluster you care about.
Overview summarizes current state with three Grafana-style gauges:
- Disk — root filesystem usage
- Memory — cluster memory usage against total capacity
- CPU — processor load against total cores
Sample numbers in the tutorial screenshot are illustrative only; always trust the live values for your own cluster.
When to use it
Check CPU, memory, and workload status after you deploy an app; look at capacity before you scale a node pool; and confirm a cluster is healthy after create or upgrade.
Tutorial: check health in the portal
Open Monitoring
From the products sidebar, open the pulse icon (Monitoring).
Stay on Metrics
Keep the Metrics tab active to see capacity gauges. Switch to Factors later if you need that companion view.
Pick the cluster and filters
Select the right cluster. Set the time range and refresh interval so they match the change you just made (for example the last few hours after a deploy).
Read Overview
In Overview, review the Disk, Memory, and CPU gauges. A sudden memory or CPU spike can explain Pending pods or resource pressure; treat a filling root disk as urgent.
Complements, does not replace:
Portal monitoring complements, but does not replace, your application APM and log pipelines.