Skip to main content
The Cluster Metrics page provides real-time visualization of your cluster’s resource usage. Metrics work out of the box: the Ankra agent ships node and pod metrics to the platform. Connecting your own Prometheus is optional, for deeper queries.

​
Overview

Ankra’s metrics visualization helps you understand your cluster’s health and resource consumption at a glance. View CPU usage, memory consumption, network throughput, disk I/O, and pod restart patterns, all from a single dashboard.

​
Accessing Cluster Metrics

  1. Navigate to your cluster from the sidebar.
  2. Click Metrics in the cluster navigation.
  3. View real-time charts and summary cards.
Built-in platform metrics need no setup and take precedence while they are healthy for the cluster. A connected Prometheus stays available as the deep-dive path - see Prometheus Integration.

​
Summary Cards

At the top of the metrics page, summary cards show current resource utilization: These cards provide instant visibility into cluster health without scrolling through detailed charts.

​
Metrics Charts

​
CPU Usage

Visualize CPU consumption across your cluster nodes over time. What it shows:
  • Per-node CPU usage lines
  • Total cluster CPU trend
  • Usage patterns over the selected time range
Use cases:
  • Identify nodes with consistently high CPU usage
  • Spot CPU spikes that correlate with deployments or traffic
  • Plan capacity based on usage trends

​
Memory Usage

Track memory consumption across your cluster. What it shows:
  • Per-node memory usage
  • Memory pressure indicators
  • Historical memory trends
Use cases:
  • Detect memory leaks in applications
  • Identify nodes approaching memory limits
  • Plan memory allocation for new workloads

​
Network I/O

Monitor network traffic flowing in and out of your cluster. What it shows:
  • Receive: Inbound network traffic per node
  • Transmit: Outbound network traffic per node
  • Throughput rates in bytes/second
Use cases:
  • Identify network-intensive workloads
  • Detect unusual traffic patterns
  • Monitor data transfer costs

​
Disk I/O

Track disk read and write operations across nodes. What it shows:
  • Disk read throughput
  • Disk write throughput
  • I/O patterns per node
Use cases:
  • Identify storage bottlenecks
  • Monitor database disk activity
  • Plan storage capacity

​
Pod Restarts

Monitor pod restart frequency to detect stability issues. What it shows:
  • Pod restart counts over time
  • Restart patterns by namespace or workload
  • Correlation with other events
Use cases:
  • Detect crashlooping pods
  • Identify unstable deployments
  • Troubleshoot OOMKilled containers

​
Time Range Selection

Control the time window for metrics data:

​
Changing Time Range

  1. Click the Time Range picker in the top-right corner
  2. Select a preset range or define a custom window
  3. Charts automatically update to show the selected period

​
Auto-Refresh

Keep metrics up-to-date with automatic refresh:

​
Manual Refresh

Click the Refresh button at any time to fetch the latest data immediately.

​
Connecting your own Prometheus (optional)

Connect a Prometheus you already run when you want queries beyond the built-in metrics.
1

Have a Prometheus to connect

Use an existing Prometheus, or deploy one to your cluster with a stack using the kube-prometheus-stack add-on.
2

Configure the data source

Go to cluster Settings → Integrations → Metrics and enter your Prometheus URL.
3

Test Connection

Verify the connection is successful before saving.

​
Default Prometheus URL

If using kube-prometheus-stack deployed via Ankra:

​
Troubleshooting

​
No metrics shown

Cause: Built-in metrics come from the Ankra agent, so they stop when the agent is offline or its metrics collection has been turned off (metrics_collect.enabled in the agent Helm values). Solution:
  1. Check the agent is online in cluster Settings → General
  2. Or connect your own Prometheus under Settings → Integrations → Metrics

​
”Unable to Load Metrics”

Cause: Connection to Prometheus failed. Solutions:
  • Verify Prometheus is running in your cluster
  • Check the Prometheus URL is correct
  • Ensure network connectivity between the Ankra agent and Prometheus
  • Review Prometheus service account permissions

​
Missing Data for Some Metrics

Cause: Prometheus may not be scraping all required metrics. Solutions:
  • Verify node-exporter is deployed for node metrics
  • Check kube-state-metrics is running for Kubernetes metrics
  • Review Prometheus scrape configurations

Prometheus Integration

Set up Prometheus for your cluster.

Alerts

Configure alerts based on metrics.

Cluster Settings

Configure metrics data sources.

AI Assistant

Use AI to analyze performance issues.