Prometheus & Grafana Integration
Wave does not replace your monitoring stack. Prometheus scrapes the metrics Wave Core exposes, and Grafana shows them next to your dashboards.
Your team already checks 5 observability tools. Wave should not be the 6th.
New Relic, 2026 Observability Forecast (the average tool count rose from 4.4 to 5.0); prometheus.io, Storage; Wave Helm values docs.
A new tool that keeps its metrics to itself adds one more place to look, and a second copy of the same data.
Wave keeps its own data for 14 days by default (WA_DATA_SAVE_DAYS). Prometheus keeps 15 days by default (prometheus.io), or as long as you set.
5 tools: New Relic, 2026 Observability Forecast (an average of 5.0). /metrics: Wave API reference. 14 days: the WA_DATA_SAVE_DAYS default, Wave Helm values docs. Tool names other than Prometheus and Grafana are illustrative.
How Wave does it
Exportersnode and app metrics- scrape
Prometheuskeeps 15 days by default - PromQL
Grafanayour dashboards - and also
Wave Consoleits own UI and 14 days of data
- Wave Agentcollects with cAdvisor on each node
- gRPCWave Corekeeps 14 days by default
- /metricsPrometheusscrapes Wave Core, keeps what you set
- PromQLGrafanaWave panels next to yours
Prometheus scrapes Wave Core
Wave Core exposes /metrics in the Prometheus text format: workload state, Autopilot decisions and scaling events, Smart Sizing recommendations, and container and Pod metrics. Add it to your scrape config.
Keep metrics as long as you need
Wave keeps its own data for 14 days by default (WA_DATA_SAVE_DAYS). Once Prometheus scrapes it, the metrics stay as long as your Prometheus retention allows.
Use them in Grafana
Grafana reads Wave metrics through Prometheus, so they sit next to the dashboards your team already uses.