Bring Grafana Cloud cost into CostGraph, pulled by us or pushed by you
Grafana Cloud bills metrics, logs, traces and profiles across every stack in an
organization, so one connection covers them all.CostGraph reads Grafana Cloud as FOCUS 1.2 records at a grain of billed dimension
x stack. Where Grafana Cloud returns a per-stack breakdown for a billed dimension, cost
is attributed to each stack; where it does not, that dimension arrives as a single
organization-level row.
Open Settings -> Integrations and pick Grafana Cloud.
Name the connection, pick the tenant these charges belong to, and enter your
organization slug, the {org} in grafana.com/orgs/{org}.
Create an Access Policy token whose realm is the organization, carrying the
billing read scopes: billing-metrics:read, org-billing-info:read,
org-billing-rate:read, invoices:read and orgs:read. Paste it in.
Select Connect.
The token must be an organization Access Policy token, which starts with glc_. A
stack service account token, starting with glsa_, cannot read billing and will fail
verification.
CostGraph verifies the token with a short fetch before saving, so a wrong value or a
missing scope fails while you are still on the form.
Credentials are encrypted at rest and used only to read billing data. Revoke the token
in Grafana Cloud at any time and the connection stops; nothing else is affected.
Records land as raw billing rows, are normalised into line items, and roll up into
daily cost. From there Grafana Cloud spend appears in Cost Overview and in anomaly
detection alongside every other provider, attributed per stack wherever Grafana Cloud
breaks the dimension down that way, and at the organization level where it does not.