ACTIVATE provides built-in observability charts for Kubernetes workloads. CPU, memory, and storage usage are collected from the Kubernetes metrics-server and displayed as time-series charts on each workload's detail page.
Metrics are available on the detail page for workload-level resources (Deployments, StatefulSets, DaemonSets, Jobs, CronJobs, and ReplicaSets). To view them:
Workload-Level Only
Metrics are shown for workload-level resources, not individual pods. To view metrics for a Deployment, click on the Deployment itself rather than one of its pods.
The Observability panel displays three charts side by side:
Shows CPU consumption in cores over time. The chart plots:
Shows memory consumption in GB over time. The chart plots:
Shows ephemeral storage consumption in GiB over time. The chart plots:
Ephemeral Storage
Storage metrics are collected from the Kubernetes node's /stats/summary endpoint and reflect ephemeral storage usage, not persistent volume usage. For persistent volume information, see Services & Storage.
A dropdown in the Observability panel header lets you select the time window for all three charts:
| Option | Description |
|---|---|
| 1 Hour | Show metrics from the last 1 hour |
| 3 Hours | Show metrics from the last 3 hours |
| 8 Hours | Show metrics from the last 8 hours (default) |
The selected time range applies to all three charts simultaneously. The default view is 8 Hours, giving you a broad view of workload behavior.
Metrics data refreshes automatically. There is no need to manually reload the page — the charts update in place with the latest data points from the metrics-server.
ACTIVATE collects metrics from the Kubernetes metrics-server, which must be installed on each connected cluster. The metrics-server provides point-in-time CPU and memory usage for pods and nodes.
The platform's metrics collection process works as follows:
PodMetrics API (metrics.k8s.io/v1beta1)/stats/summary proxy endpointMetrics Server Required
If the metrics-server is not installed on a cluster, the Observability panel will not display any data. Ensure that metrics-server is deployed and running in the kube-system namespace of each cluster you want to monitor.
Metrics aggregation resolves each pod's owner to determine which workload it belongs to:
| Pod Owner | Resolved Workload |
|---|---|
| ReplicaSet (owned by Deployment) | Deployment |
| StatefulSet | StatefulSet |
| Job | Job |
| DaemonSet | DaemonSet (excluded from metrics) |
| Standalone pod | Excluded |
Excluded Workloads
DaemonSet pods and standalone pods (pods with no owner reference) are excluded from workload-level metrics collection because they are not typically associated with a user-managed workload.