Skip to main content
Confluent Cloud bills per product and resource, so Kafka spend is attributed per cluster and environment. CostGraph reads Confluent Cloud as FOCUS 1.2 records at a grain of billing line item (product x resource).

​
Choose how the data reaches us

CostGraph pulls it

You supply read-only credentials and we call Confluent 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

  • Create a Cloud API key that isn’t tied to a cluster: confluent api-key create --resource cloud.
  • Give the key an org-level billing role, OrganizationAdmin or BillingAdmin. A resource-scoped key, or a key without a billing role, returns 403.

​
Let CostGraph pull

  1. Open Settings > Integrations and pick Confluent Cloud.
  2. Name the connection and pick the tenant these charges belong to.
  3. Enter the values you copied. The form lists what Confluent Cloud needs and marks the optional ones.
  4. Select Connect.
CostGraph verifies the credentials with a short fetch before saving, so a wrong value or a missing permission fails while you are still on the form.
Credentials are encrypted at rest and used only to read billing data. Revoke them in Confluent 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 Confluent 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 Confluent 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 Confluent Cloud spend appears in Cost Overview and in anomaly detection alongside every other provider.