​
Overview

This feature is available with Conduktor Scale Plus only.
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, facilitating cost accountability and management.

​
Prerequisites

Chargeback requires both Console (v1.29.0 and above) and Gateway (v3.4.0 and above).

​
Enable Chargeback in Console

To enable the Chargeback in Console:
  1. Go to Settings > Clusters and select your cluster.
  2. In the Provider tab, Select Gateway and enter the API details with the default Virtual Cluster value of passthrough. Gateway provider
  3. Deploy the Chargeback Interceptor on Gateway. This can be done using:
Go to the Kafka Gateway page and search for observability. Open the observability-interceptor and paste your configuration:
{
  "name": "observability-interceptor",
  "pluginClass": "io.conduktor.gateway.interceptor.observability.ObservabilityPlugin",
  "priority": 100,
  "config": {
    "topicName": "_conduktor_observability",
    "replicationFactor": 3,
    "flushIntervalInSecond": 300
  }
}
After a few minutes, you should see your active service accounts appear on the Chargeback page in Console.

​
Chargeback Interceptor

This Interceptor will watch produce and consume to store metrics about incoming and outgoing traffic (bytes) in a topic. The topic is then utilized by the Console to display Chargeback metrics.

​
Configure Chargeback Interceptor

NameTypeDefaultDescription
topicNameStringTopics used to store observability metrics. If this topic already exists in your cluster, it has to have only one partition. If the topic doesn’t exist, Gateway will create it when you deploy the plugin.
replicationFactorIntThe replication factor to set if Gateway needs to create the topic.
flushIntervalInSecondInt300The periodic interval for flushing metrics to the specified topic.