Chargeback is a cost allocation feature that enables organizations to track, visualize and attribute Kafka infrastructure costs to different clusters, teams or departments.By measuring resource consumption over time, Chargeback helps you understand Kafka spending, promote cost accountability and make informed decisions about resource optimization.Conduktor offers two types of Chargeback:
with Gateway: tracks bytes produced/consumed by
without Gateway: (introduced in Console v1.41.0) tracks storage and partitions. These metrics can be viewed by cluster, application, application instance and topic.
If you’re using Console v1.41.0 or above, you have to set CDK_CHARGEBACKV2_ENABLED environment variable to true to continue using Chargeback.
Chargeback with Gateway (previously known as Chargeback) allows organizations to track and allocate costs/usage associated with Kafka resources to different teams or departments, based on their data consumption and processing. This facilitates cost management and accountability.The tracked metrics are: bytes produced and consumed by service accounts.
Enables organizations to track and allocate costs associated with Kafka topics. Does not require Gateway.Chargeback collects metrics directly from Console’s metadata indexer which queries topic, partition and storage information from your Kafka clusters.
Metric
Description
Storage
Total bytes stored across topics
Partition count
Number of partitions across topics
You can:
Value: calculate average bytes and average partitions
Cost tracking: calculate costs (in USD) for storage and partitions
Multiple views: view overall costs, storage costs and partition costs
Granularity: track costs per cluster, application, application instance and topic
Percentage attribution: see the percentage of total costs per item
