Monitor Confluent Platform with Confluent for Kubernetes¶
Monitor your Confluent for Kubernetes (CFK) environment using the following tools and resources:
- Confluent Health+ with Telemetry
- JMX metrics monitoring integrations
- Confluent Control Center
Confluent Health+ provides ongoing, real-time analysis of performance and configuration data for your Confluent Platform deployment. From this analysis, Health+ sends out notifications to alert users to potential environmental issues before they become critical problems.
For more information, see Confluent Health+.
The Confluent Telemetry Reporter is a plugin that runs inside each Confluent Platform service to push metadata about the service to Confluent. Telemetry Reporter enables product features based on the metadata, like Health+. Data is sent over HTTP using an encrypted connection.
Telemetry is enabled by default and is configured globally at the CFK level. However, you have an option to disable for specific Confluent Platform components.
Each Confluent Platform component CR provides the status condition, in
whether Telemetry is enabled or disabled.
For more information and supported settings for Telemetry Reporter, see Confluent Telemetry Reporter.
For a list of metrics that are collected for Health+, see Telemetry Reporter Metrics.
Globally configure Telemetry¶
The Telemetry Reporter settings are in the CFK values file and managed globally for all Confluent Platform components:
telemetry: enabled: ---  secretRef: ---  directoryPathInContainer: --- 
 Set it to
falseto globally disable Telemetry Reporter.
  CFK supports the
directoryPathInContainermethods to load Telemetry configuration through Helm.
secretReftakes the precedence over
directoryPathInContainerif both are configured.
secretRefmust contain the following:
telemetry.txt : |- api.key=<cloud_key> api.secret=<cloud_secret> proxy.url=<proxy_url> proxy.username=<proxy_username> proxy.password=<proxy_password>
If the referenced
secretRefis not read or data is not in the expected format, CFK will fail to start.
 Provide the mount path or directory path where
telemetry.txtis present. The
telemetry.txtshould contain the following:
api.key=<cloud_key> api.secret=<cloud_secret> proxy.url=<proxy_url> proxy.username=<proxy_username> proxy.password=<proxy_password>
telemetry.txtis not in the expected format, CFK will fail to start.
To apply changes in Telemetry settings, in the referenced Secret, or in the
telemetry.txt file, you must manually restart CFK and Confluent Platform:
kubectl rollout restart deployment/confluent-operator
Restart a Confluent Platform component:
kubectl rollout restart sts/<name>
See Restart Confluent Platform Cluster for looking up
<name>of a component.
Disable Telemetry for a Confluent Platform component¶
To disable Telemetry for a specific Confluent Platform component, set the following in the
component CR and apply the change with the
kubectl apply command:
telemetry: global: false
CFK deploys all Confluent components with JMX metrics enabled by default. These JMX metrics are made available on all pods at the following endpoints:
- JMX metrics are available on port 7203 of each pod.
- Jolokia (a REST interface for JMX metrics) is available on port 7777 of each pod.
Configure security on JMX metrics endpoints¶
By default, authentication, encryption, and external access are not provided on JMX/Prometheus metric endpoints, but you have options to configure authentication, TLS, and external access for JMX/Prometheus metric endpoints at the component CR level:
metrics: authentication: type: ---  prometheus: ---  rules: blackList: whiteList: tls: enabled: --- 
 Set to
mtlsfor mTLS authentication.
If you set this to
mtls, you must set
 Specify Prometheus configurations to override the default settings.
 If set to
true, metrics are configured with global or component TLS as described in Configure Network Encryption with Confluent for Kubernetes.
Confluent Control Center¶
Confluent Control Center is a web-based tool for managing and monitoring Confluent Platform. Control Center provides a user interface that enables developers and operators to:
- Get a quick overview of cluster health
- Observe and control messages, topics, and Schema Registry
- Develop and run ksqlDB queries
For the metrics available for monitoring, see Metrics available in Control Center.
Configure Control Center to monitor Kafka clusters¶
The Confluent Metrics Reporter collects various metrics from an Apache Kafka® cluster. Control Center then uses those metrics to provide a detailed monitoring view of the Kafka cluster.
By default, the Confluent Metrics Reporter is enabled and configured to send metrics for the Kafka cluster to a set of topics on the same Kafka cluster.
To send metrics to a different cluster, or to configure specific authentication settings, configure the Kafka custom resource (CR):
metricReporter: enabled: ---  authentication: type: ---  jaasConfigPassThrough: secretRef: ---  tls: enabled: --- 
-  Set to
falseto enable or disable the metrics reporting.
-  Set to the authentication type to use for Kafka. See Configure authentication to access Kafka for details.
-  Set to the Kubernetes Secret name used to authenticate to Kafka.
-  Set to
trueif the Kafka cluster has TLS network encryption enabled.
Once Confluent Metrics Reporter is setup for a Kafka cluster, configure Control Center to monitor the cluster.
By default, Control Center is set up to monitor the Kafka cluster it is using to store its own state.
If there is another Kafka cluster to monitor, you can configure that in the Control Center CR as below:
spec: monitoringKafkaClusters: - name: ---  bootstrapEndpoint: --- 
-  Set to Kafka cluster name.
-  Set to the Kafka bootstrap endpoint.
Configure Control Center to monitor ksqlDB and Connect clusters¶
You can configure Control Center to provide a detailed monitoring view of ksqlDB and Connect clusters.
For an example to configure Confluent Control Center to monitor multiple ksqlDB and Connect clusters, see Connect Control Center to Multiple Connect and ksqlDB Clusters.