Installing Control Center¶
Confluent Control Center is included in the Confluent Platform Enterprise package.
Prerequisite
- Confluent Platform Enterprise Edition is installed. You can get up and running with the full Confluent platform quickly on a single server or you can Deploy using Docker.
Configure Kafka and Kafka Connect¶
Before starting Control Center, you must update the Kafka and Kafka Connect configuration files.
Uncomment these lines in the Kafka server configuration file (
<path-to-confluent>/etc/kafka/server.properties
). This enables Confluent Metrics Reporter.Tip: Before making these changes, make a backup copy of the default Kafka server configuration file.
##################### Confluent Metrics Reporter ####################### # Confluent Control Center and Confluent Auto Data Balancer integration # # Uncomment the following lines to publish monitoring data for # Confluent Control Center and Confluent Auto Data Balancer # If you are using a dedicated metrics cluster, also adjust the settings # to point to your metrics kakfa cluster. metric.reporters=io.confluent.metrics.reporter.ConfluentMetricsReporter confluent.metrics.reporter.bootstrap.servers=localhost:9092 # # Uncomment the following line if the metrics cluster has a single broker confluent.metrics.reporter.topic.replicas=1
Add these lines to the Kafka Connect properties file (
<path-to-confluent>/etc/kafka/connect-distributed.properties
). This will add support for the interceptors.# Interceptor setup consumer.interceptor.classes=io.confluent.monitoring.clients.interceptor.MonitoringConsumerInterceptor producer.interceptor.classes=io.confluent.monitoring.clients.interceptor.MonitoringProducerInterceptor
For more information, see Installing Control Center Interceptors.
Start Confluent Platform.
$ confluent start
Your output should resemble this:
Starting zookeeper zookeeper is [UP] Starting kafka kafka is [UP] Starting schema-registry schema-registry is [UP] Starting kafka-rest kafka-rest is [UP] Starting connect connect is [UP]
Configure and start Control Center¶
Tip: Start Control Center in its own terminal since this is a long running process.
Define the number of partitions (
<num-partitions>
) and replication (<num-replication>
) settings for Control Center by adding these lines to your properties file (<path-to-file>/etc/confluent-control-center/control-center.properties
).# Quickstart partition and replication values confluent.controlcenter.internal.topics.partitions=<num-partitions> confluent.controlcenter.internal.topics.replication=<num-replication> confluent.controlcenter.command.topic.replication=<num-replication> confluent.monitoring.interceptor.topic.partitions=<num-partitions> confluent.monitoring.interceptor.topic.replication=<num-replication> confluent.metrics.topic.partitions=<num-partitions> confluent.metrics.topic.replication=<num-replication>
Start Control Center with your properties file specified.
$ <path-to-confluent>/bin/control-center-start <path-to-file>/etc/confluent-control-center/control-center.properties
You can navigate to the Control Center web interface at http://localhost:9021/.
To use Control Center, users must have access the host that runs the application. (You can configure the network port that Confluent Control Center uses to serve data.) Because Confluent Control Center is a web application, you may use a proxy to control and secure access to it.
For a complete example that includes stream monitoring, see the controlcenterquickstart.