You can configure Confluent Control Center through a configuration file that is passed to Control Center on start.
Parameters are provided in the form of key/value pairs. Lines beginning with # are ignored.

In almost all installations, you will want to configure these parameters:

bootstrap.servers

A list of host/port pairs to use for establishing the initial connection to the Kafka cluster. The client will make
use of all servers irrespective of which servers are specified here for bootstrapping; this list only impacts the
initial hosts used to discover the full set of servers. This list should be in the form
host1:port1,host2:port2,.... Since these servers are just used for the initial connection to
discover the full cluster membership (which may change dynamically), this list need not contain the full set of
servers (you may want more than one, though, in case a server is down).

Type: list

Default: “localhost:9092”

Importance: high

zookeeper.connect

Specifies the ZooKeeper connection string in the form
hostname:port where host and port are the host and port of a ZooKeeper server. To allow connecting
through other ZooKeeper nodes when that ZooKeeper machine is down you can also specify multiple hosts
in the form hostname1:port1,hostname2:port2,hostname3:port3,...
The server may also have a ZooKeeper chroot path as part of it’s ZooKeeper connection string which puts
its data under some path in the global ZooKeeper namespace. If so the consumer should use the same
chroot path in its connection string. For example, for a chroot path of /chroot/path, you would specify
the connection string as hostname1:port1,hostname2:port2,hostname3:port3/chroot/path.

Type: list

Default: “localhost:2181”

Importance: high

confluent.controlcenter.connect.cluster

Comma-separated list of URLs for the Connect cluster

Type: string

Default: “localhost:8083”

Importance: high

confluent.controlcenter.connect.zookeeper.connect

Specifies the ZooKeeper connection string for the Kafka cluster backing the Connect cluster

Type: string

Default: the value of zookeeper.connect

Importance: high

confluent.controlcenter.license

Confluent will issue a license key to each subscriber, allowing the subscriber to unlock the full functionality
of Control Center. The license key will be a short snippet of text that you can copy and paste. Paste this value
into the license key. If you do not provide a license key, Control Center will stop working after 30 days. If you
are a subscriber, please contact Confluent Support for more information.

We allow you to change some other parameters that change how Control Center behaves, such as internal topic
names, data file locations, and replication settings. The default values for most of these settings are suitable for
production use, but you can change these if needed.

confluent.controlcenter.rest.listeners

Comma-separated list of listeners that listen for API requests over either http or https. If a listener uses https,
the appropriate SSL configuration parameters need to be set as well.

Controls default consumer behavior when no previously committed offsets are present.
Set this to “latest” if you do not want to process any historical stream monitoring
data (which can take some time) on initial start-up. Note that once any offsets are
committed, this setting has no effect on subsequent restarts.

Type: string

Default: “earliest”

Importance: high

confluent.controlcenter.id

Identifier used as a prefix so that multiple instances of Control Center can co-exist.

Type: string

Default: 1

Importance: low

confluent.controlcenter.command.topic

Topic used to store Control Center configuration

Type: string

Default: “_confluent-command”

Importance: low

confluent.monitoring.interceptor.topic

The durable topic that acts as the durable log for the data

Type: string

Default: “_confluent-monitoring”

Importance: low

confluent.controlcenter.name

Control Center Name

Type: string

Default: “_confluent-controlcenter-3-1-0”

Importance: low

confluent.controlcenter.internal.topics.partitions

Number of partitions used internally by Control Center.

Type: integer

Default: 4

Importance: low

confluent.controlcenter.internal.topics.replication

Replication factor used internally by Control Center.

Type: integer

Default: 3

Importance: low

confluent.controlcenter.internal.topics.retention.ms

Maximum time in milliseconds that internal data is stored in Kafka.

Type: long

Default: 86400000

Importance: low

confluent.controlcenter.internal.topics.changelog.segment.bytes

Segment size in bytes for internal changelog topics in Kafka. This must be as small
as broker settings log.cleaner.dedupe.buffer.size / log.cleaner.threads to
guarantee enough space in the broker’s dedupe buffer for compaction to work.

Security parameters must be set on both producers and consumers. The prefix for producer
settings is confluent.controlcenter.streams.producer and the prefix for consumer
settings is confluent.controlcenter.streams.consumer.

Because Control Center reads and writes data to Kafka, we also allow you to change some producer and consumer configurations. We do not recommend changing these values unless advised by Confluent Support. Some examples of values used internally are given. These settings map 1:1 with producer/consumer configs used internally by Confluent Control Center and all use the prefix confluent.controlcenter.streams.{producer,consumer}..

confluent.controlcenter.streams.num.stream.threads

The number of threads to execute stream processing

Type: integer

Default: 8

Importance: low

confluent.controlcenter.streams.consumer.session.timeout.ms

The timeout used to detect a consumer failure

Type: integer

Default: 275000

Importance: low

confluent.controlcenter.streams.consumer.request.timeout.ms

The maximum amount of time the client will wait for the response of a request