Skip to main content
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.

​
Choose how the data reaches us

CostGraph pulls it

You supply a read-only token and we call Grafana Cloud once a day. Nothing to run.

You push it

You send us FOCUS records over the API. Credentials never leave your infrastructure.

​
Before you begin

  • In Grafana Cloud, create an Access Policy whose realm is the organization, with the billing-metrics:read, org-billing-info:read, org-billing-rate:read, invoices:read, and orgs:read scopes. Create a token for it.
  • The token must be an organization access policy token, which starts with glc_. A stack service account token, which starts with glsa_, can’t read billing.
  • Note the organization slug, the {org} in grafana.com/orgs/{org}.

​
Let CostGraph pull

  1. Open Settings > Integrations and pick Grafana Cloud.
  2. Name the connection, pick the tenant these charges belong to, and enter your organization slug, the {org} in grafana.com/orgs/{org}.
  3. Enter the access policy token.
  4. 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.

​
Push it yourself

Send the charges to CostGraph as FOCUS records instead. Push FOCUS data covers the connection id, the focus:write key, and the request shape.

​
Run the exporter

Rather than build that request yourself, run our exporter. It reads Grafana Cloud on a schedule and pushes the records for you, wherever you want to run it: a container, a Kubernetes CronJob, or a binary on a machine you already have.
Your Grafana Cloud credential stays where you put it, and only the finished FOCUS records reach CostGraph. Run the exporter covers the three ways to run it and the variables it reads.

​
What CostGraph does with it

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.