Grafana Cloud cost management - usage monitoring, cost attribution by label, usage alerts, invoice management, and optimization strategies. Covers Adaptive Metrics (cardinality reduction), Adaptive Logs (log…
---
name: cost-management
license: Apache-2.0
description: Cut your Grafana Cloud bill by attributing spend to teams and reducing telemetry volume. Covers FOCUS-compliant billing dashboards, cost-attribution labels in Alloy, Adaptive Metrics (cardinality reduction), Adaptive Logs (drop/sample), Adaptive Traces (tail sampling), usage alerts, and an optimization checklist. Use when investigating a high Grafana Cloud bill, attributing observability cost to a team or service, reducing active series / log bytes / trace spans, or setting up usage / quota alerts — even when the user says "our Grafana bill is too high", "who's burning the most metrics", "drop debug logs", "sample our traces", or "alert me before we hit quota" without naming Cost Management.
---
# Grafana Cloud Cost Management
> **Docs**: https://grafana.com/docs/grafana-cloud/cost-management-and-billing/
Reduce metric / log / trace spend with Adaptive signals + cost-attribution labels.
## Prerequisites
- A Grafana Cloud stack with Adaptive Metrics / Logs / Traces enabled (visible under **Cost Management**)
- Alloy (or Grafana Agent) ingesting telemetry, with API key in scope `metrics:write` + `logs:write` (+ `traces:write`)
- Admin access to the stack to apply Adaptive recommendations
## Common Workflows
### 1. Attribute cost to a team / service
```alloy
# 1. Add external labels in Alloy (metrics + logs configs)
prometheus.remote_write "cloud" {