Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.conduktor.io/llms.txt

Use this file to discover all available pages before exploring further.

Enterprise

​
Overview

Chargeback shows Kafka costs across four axes — storage, partitions, ingress and egress — and lets you group those costs by cluster, application or label. Each row supports drill-down into topics and service accounts. For background on the four cost axes and the metrics available per cluster type, see Chargeback concepts.

​
Set up Chargeback

The first time an administrator opens the Chargeback page, an onboarding wizard runs through two steps:
1

Set cost rates

For each cluster, enter the unit costs that match your provider pricing or internal infrastructure model:
FieldUnitRequired
Bytes stored$/GB/hourYes
Partitions$/partition/hourYes
Ingress$/GBNo
Egress$/GBNo
Each value supports up to eight decimal places, with a maximum of 9.99999999. Leaving ingress or egress empty is the same as 0.
2

Select Chargeback Labels

Pick the label keys you want to group costs by (for example, team, cost-center, env).Only labels currently attached to topics or service accounts are offered. Conduktor-defined labels (the conduktor.io/* namespace) are excluded.You can skip this step and add Chargeback Labels later from the settings drawer.
After both steps are saved, Console begins applying these rates to the metrics already collected.

​
View costs

Use the filter bar at the top of the page to control what’s displayed.
ControlWhat it does
View byGroup rows by Cluster, Application, Application Instance, or one of the configured Chargeback Labels
ShowPick which cost columns to display (Overall, Storage, Partitions, Ingress, Egress)
PeriodSwitch between 7D, 30D, 6M, 12M and YTD
SearchNarrow the rows by name match within the current view
The chart at the top shows the totals for the active view across the selected period. The table below lists each entity with its measured value, calculated cost and percentage of the total.

​
Drill into topics and service accounts

Each row in the Cluster, Application Instance and Label views can be expanded to show the topics and service accounts that contributed to it.
  • Topics: storage, partitions, ingress and egress per topic
  • Service accounts: ingress and egress per service account
Service account drill-downs depend on the cluster type. See the cluster-type capability matrix in Chargeback concepts.

​
How metrics are calculated

Metrics are stored as raw counters and costs are computed at query time. Updating a unit cost takes effect immediately across all historical periods. 
storage_cost = (byte_hours / 1,073,741,824) × bytes_stored_per_hour_cost
1,073,741,824 is one GB in bytes (1024³). byte_hours accumulates from periodic snapshots: each snapshot multiplies the topic’s current retained bytes by the snapshot interval expressed in hours.
The accuracy of storage and partition metrics depends on the snapshot frequency. A shorter interval captures more granular usage; a longer interval may miss short-lived spikes.Deleting a cluster removes its Chargeback metrics.

​
Update cost rates and labels

Click the settings (cog) icon at the top right of the Chargeback page to open the settings drawer:
  • General tab: edit cost rates per cluster, or add a new cluster row
  • Chargeback Labels tab: add or remove the label keys eligible for grouping
Both tabs save independently.

​
Export data

Click Export in the filter bar to download the current view as a CSV. The export reflects the active View by, Show selections, Period and Search, so only data matching your current view is included. The default file name is Chargeback_<startDate>_<endDate>_<view>.csv. The granularity of the exported series matches the selected period: 7D and 30D split by day, 6M, 12M and YTD split by month.

​
Permissions

ActionRequired permission
View costs and drill-downsCan view Chargeback (PlatformChargebackView)
Set cost ratesCan manage Chargeback (PlatformChargebackManage)
Select Chargeback LabelsCan manage Chargeback (PlatformChargebackManage)
Console shows cost attribution for all clusters regardless of the cluster-level permissions assigned to the user.