
For details about using this connector with Kafka Connect Reporter, see Connect Reporter. This configuration is used typically along with standalone workers. Put this file inside the Confluent Platform installation directory.
Kafka connect prometheus exporter how to#
For example, a 16-node Kubernetes cluster with 16 Cloud Native Application Observability Distribution for OpenTelemetry™ Collector replicas can handle a total of 80,000 Kafka partitions. This document describes how to configure your Google Kubernetes Engine deployment so that you can use Google Cloud Managed Service for Prometheus to collect. Create a configuration file prometheus-metrics-sink.properties with the following content. To process additional partitions, add one Cloud Native Application Observability Distribution for OpenTelemetry™ Collector replica for every 5,000 partitions. The JAR file should be copied on all of the servers where Prometheus clients reside, and it will be activated using the. Prometheus exporter for Confluent Cloud Metrics API. This limit ensures that you have enough storage for Cloud Native Application Observability metrics, events, logs, and traces (MELT) data. To set up the Prometheus client exporter configuration for all Confluent components, we need the following: JMX exporter JAR file: This file is responsible for exposing all of the JVM metrics in a Prometheus-compatible format. For instance, you can POST a query written in JSON and get back connector information specified by. See Prometheus Exporters and integrations.Įach Cloud Native Application Observability Distribution for OpenTelemetry™ Collector replica can process 5,000 Kafka partitions. Grafana Labs provides dashboard visualizations of Prometheus metrics.

Kafka Exporter adds additional Prometheus metrics. The JMX exporter can export from a wide variety of JVM-based applications, for example Kafka and Cassandra. The Prometheus Alertmanager plugin handles alerts and routes them to a notification service.
Kafka connect prometheus exporter install#
If you don’t have the Cloud Native Application Observability Helm chart installed, see Install Kubernetes and App Service Monitoring.īefore you integrate Prometheus, you must h ave configured Kafka and JMX exporters in your environment. Prometheus pulls metrics from Kafka, ZooKeeper and Kafka Connect clusters. The Cloud Native Application Observability Helm chart package provides all the necessary dependencies. This page explains how to use add the Kafka Prometheus exporter within your deployed environment using Helm Charts. Kafka Connect, through configuration, exposes a Prometheus endpoint for Kafka connect metrics to be pulled.
