Overview

This repo demonstrates examples of JMX monitoring stacks that can monitor Confluent Platform. While Confluent Control Center provides an opinionated view of Apache Kafka monitoring, JMX monitoring stacks serve a larger purpose to our users, allowing them to setup monitoring across multiple parts of their organization, many outside of Kafka, and to have a single pane of glass.

Caution

The examples in this repo may not be complete and are for testing purposes only. They serve only to demonstrate how the integration works with Confluent Platform.

How to run with cp-demo

This repo is intended to be run specifically with cp-demo. Make sure you have enough system resources on the local host to run this. Verify in the advanced Docker preferences settings that the memory available to Docker is at least 8 GB (default is 2 GB).

NOTE: If there is interest to test Kafka Lag Exporter (included on the monitoring stacks) make sure to use JDK 8 when running the demo, as it requires JDK8-generated certificates for the container to work (seglo/kafka-lag-exporter#270).

Ensure that cp-demo is not already running on the local host.
Decide which monitoring stack to demo: either jmxexporter-prometheus-grafana or metricbeat-elastic-kibana and set the MONITORING_STACK variable accordingly.

# Set one of these
MONITORING_STACK=jmxexporter-prometheus-grafana
MONITORING_STACK=metricbeat-elastic-kibana

Clone cp-demo and checkout 7.2.0-post (this has been validated only with cp-demo in the 7.2.0-post branch).

[[ -d "cp-demo" ]] || git clone https://github.com/confluentinc/cp-demo.git
(cd cp-demo && git fetch && git checkout 7.2.0-post && git pull)

Clone jmx-monitoring-stacks and checkout a compatible release.

[[ -d "jmx-monitoring-stacks" ]] || git clone https://github.com/confluentinc/jmx-monitoring-stacks.git
(cd jmx-monitoring-stacks && git fetch && git checkout 7.2-post && git pull)

Start the monitoring solution with the STACK selected. This command also starts cp-demo, you do not need to start cp-demo separately.

${MONITORING_STACK}/start.sh

Stop the monitoring solution. This command also stops cp-demo, you do not need to stop cp-demo separately.

${MONITORING_STACK}/stop.sh

How to run with CCloud "/export" endpoint (openMetrics endpoint)

The demo with CCloud needs a CCloud Instance running and you (as a user) are required to gather some details before spinning up the CCloud monitoring solution. Please refer to this README for detailed steps to run a CCloud based sample dashboard.

How to use with cp-ansible

To add JMX exporter configurations from this project into cp-ansible add the following configurations:

    zookeeper_jmxexporter_config_source_path: ../jmx-monitoring-stacks/shared-assets/jmx-exporter/zookeeper.yml
    kafka_broker_jmxexporter_config_source_path: ../jmx-monitoring-stacks/shared-assets/jmx-exporter/kafka_broker.yml
    schema_registry_jmxexporter_config_source_path: ../jmx-monitoring-stacks/shared-assets/jmx-exporter/confluent_schemaregistry.yml
    kafka_connect_jmxexporter_config_source_path: ../jmx-monitoring-stacks/shared-assets/jmx-exporter/kafka_connect.yml
    kafka_rest_jmxexporter_config_source_path: ../jmx-monitoring-stacks/shared-assets/jmx-exporter/confluent_rest.yml
    ksql_jmxexporter_config_source_path: ../jmx-monitoring-stacks/shared-assets/jmx-exporter/confluent_ksql.yml

Add and execute the Ansible template task here to generate the Prometheus configuration for your Ansible inventory.

tsuz/jmx-monitoring-stacks

Overview

Caution

How to run with cp-demo

How to run with CCloud "/export" endpoint (openMetrics endpoint)

How to use with cp-ansible

See Also