Integration · Queues & brokers
Apache Kafka
Topic lag, ISR, controller metrics, JMX.
What gets collected
A JMX exporter sidecar on every broker. Metrics: per-topic message rate, under-replicated partitions, consumer group lag, leader election count.
Requirements
- ✓Kafka 2.x+ / KRaft
- ✓JMX enabled per broker
- ✓JMX exporter sidecar
Key metrics
Collected out of the box. Every metric is available in dashboards, alerts and PromQL.
kafka.topic.msg.ratekafka.partition.under_replicatedkafka.consumer.lagkafka.controller.countkafka.leader.electionsSetup steps
- 1Enable JMX on each broker
- 2Deploy a JMX exporter sidecar
- 3
kafka-consumer-groups for lag collection
After install
- · Metrics show up on the dashboard within 15-30 seconds
- · Integration labels flow into filters automatically
- · Dashboard presets for common metrics are available in the editor
More in the docs
Apache Kafka
Frequently asked questions
- What does Unimoni collect from Apache Kafka?
- Topic lag, ISR, controller metrics, JMX. Every metric lands in the same TSDB as the rest of your stack, so you can build dashboards and alerts across Apache Kafka and everything else in one place.
- How long does it take to connect Apache Kafka?
- Usually a few minutes: a handful of steps, no code changes. Metrics show up on your dashboards within 15–30 seconds of the first scrape.
- What access does the Apache Kafka integration need?
- Only the minimum listed under Requirements above — a scoped token or role, nothing more. Unimoni asks for the least privilege each system supports.
- Is Apache Kafka monitoring available self-hosted and on the free plan?
- Yes. Every integration works identically on Unimoni Cloud and self-hosted, and is included from the free tier up.