Grafana Adaptive Metrics adds cost-first auto-apply to prevent metrics-series growth

On October 15, 2026, Grafana announced general availability of Adaptive Metrics auto-apply with a new cost-first mode alongside the existing coverage-first behaviour. Adaptive Metrics recommends aggregation rules based on how dashboards, alerts and queries use time-series detail. Cost-first automatically accepts series-reducing recommendations, then accepts series-increasing recommendations only while the projected total remains at or below the series count at the start of the cycle. Coverage-first applies both types without that constraint. Modes can be set separately by telemetry segment.

Automated dashboards, AI agents and exploratory queries can inadvertently cause metric-cardinality growth and surprise bills. Cost-first makes a bounded default available to teams that prioritise predictable active-series counts, while critical services can retain coverage-first behaviour. The tradeoff is explicit: cost-first may withhold detail that a newly issued query requests until an operator changes policy.

The new mode accepts all recommended aggregations that reduce active series, ranks series-increasing recommendations from smallest to largest, and applies them only until the original series count would be exceeded. It prevents auto-apply itself from raising the projected series count in that cycle.

Coverage-first restores raw metric detail when queries demand it, even if that increases the total series count. Grafana recommends it for critical datasets where full coverage matters more than spend predictability. The two modes can coexist in separate segments.

A coding or observability agent may issue broad exploratory queries without understanding how many metric dimensions they touch. Automatically restoring every dimension can expand series counts and cost. Cost-first provides a mechanical cap, but does not replace alert and data-retention reviews.

Existing Grafana Cloud Adaptive Metrics users can enable auto-apply per segment and choose the mode; an Admin role is required. The documentation warns that segments near their aggregation-rule limits may skip some recommendations. Teams should create exemptions for metrics that must never lose necessary detail.

Grafana's guarantee concerns projected active-series counts during an auto-apply cycle, not all usage, storage, retention, query, log or trace charges. Savings figures are vendor-reported; independent operational benchmarks are not provided in the launch.