Installation

Detailed instructions for installing the Confluent Platform are provided in our installation guide. Below are some short instructions on how to install just the Confluent Control Center server on common platforms.

Installation on RedHat, Centos, or Fedora

Confluent Control Center is included in the full Confluent Platform Enterprise package. Installation instructions for installing the overall platform on RedHat style systems can be found at RPM packages via yum.

If you would like to install just Control Center on a server, first follow the instructions for configuring Confluent repositories with you package manager. Then, you can install control center with a line like:

$ sudo yum install confluent-control-center

Installation on Debian Linux

Confluent Control Center is included in the full Confluent Platform Enterprise package. Installation instructions for the overall platform on Debian style systems can be found at DEB packages via apt.

If you would like to install just Control Center on a server, first follow the instructions for configuring Confluent repositories with you package manager. Then, you can install control center with a line like:

$ sudo apt-get install confluent-control-center

Other systems

Confluent Control Center is included in the full Confluent Platform Enterprise package. Installation instructions for installing the overall platform from archives can be found at ZIP and TAR archives.

Installing Kafka Connect

See Installing and Configuring Kafka Connect for more information about how to install and configure Kafka Connect. (You need to install Kafka Connect for Control Center to configure it.)

Installing Confluent Metrics Clients with Kafka Connect

If you install the Confluent Platform, then you already have all the software you need to monitor Kafka Connect jobs with Stream Monitoring.

If you have installed Kafka Connect separately, you can still use Stream Monitoring to monitor Kafka Connect. To do this, you need to take these steps:

  1. Upgrade to Kafka 0.10.1.0+
  2. Add the Confluent Metrics Interceptor to the Kafka Connect classpath.
  3. Add the Confluent Metrics Interceptor to the client configurations in the Kafka Connect congfig files. You can append two lines like this in your configuration file to do this:
consumer.interceptor.classes=io.confluent.monitoring.clients.interceptor.MonitoringConsumerInterceptor
producer.interceptor.classes=io.confluent.monitoring.clients.interceptor.MonitoringProducerInterceptor

Starting Control Center

We have provided a convenient script for starting control center, called controlcenter-start. This script takes one argument: a configuration file specifying properties for Control Center. For example, you can use a command like this to start control center with the default properties:

$ bin/controlcenter-start config/controlcenter.properties

If you would like to start Control Center as a daemon process, you can use the -daemon option:

$ bin/controlcenter-start -daemon config/controlcenter.properties

For information on what properties you need to specify, see Configuration.

License Keys

Confluent Control Center is proprietary software. If you have downloaded and installed this from the Confluent Web Site and are not a Confluent Enterprise subscription customer, you have already agreed to our license agreement. If you are a Confluent Enterpise subscription customer, then you are bound by the terms of the agreement between your company and Confluent.

If you are not a customer, your download includes a 30 day free trial for Control Center. Control Center will stop functioning 30 days after you install the software. Any Kafka Connect Connectors that you created will still function; you can use the Kafka Connect API to change them, but you cannot use Control Center to make changes to connectors. Stream Monitoring will continue to log data, but the web application will not continue to function. If you would like to learn more about how to become a Confluent Platform Enterprise subscription customer, please visit our web site.

If you are a customer, we will issue you a license key and all of the functions of Control Center will be unlocked for the term of your subscription. If the Stream Monitoring functionality has become disabled, please contact us through our support portal for assistance.

Removing Control Center

If you would like to remove Control Center from your system, please follow these instructions.

TAR and ZIP Archives

Inside the archive, Control Center resources can be found in the following locations:

  • Java Archives are found in share/java/confluent-control-center and share/java/monitoring-interceptors
  • Configuration files are found in etc/confluent-control-center
  • Executables are bin/control-center-start and bin/control-center-runclass

You can remove this all with a command like:

$ rm -rf share/java/confluent-control-center \
         share/java/monitoring-interceptors \
         etc/confluent-control-center \
         bin/control-center-*

Debian packages

If you installed with apt-get as a superuser, you can remove Control Center with a command like:

$ sudo apt-get remove confluent-control-center

Otherwise, follow the directions for the package management tool that you used.

Redhat packages

If you installed with yum as a superuser, you can remove Control Center with a command like:

$ sudo yum remove confluent-control-center

Otherwise, follow the directions for the package management tool that you used.