DumbMonit
用 DumbMonit 监控 Apache Kafka
The event streaming cluster: offline and under-replicated partitions, a missing controller, and the lag of the consumer groups.
产品说明为英文，与产品内一致。页面标签使用您的语言。
DumbMonit 监控的内容
Apache Kafka and compatible brokers (Redpanda, Confluent): offline and under-replicated partitions, a missing controller, and the lag of the consumer groups.
典型用途. Offline and under-replicated partitions, controller, consumer group lag
示例
- Apache Kafka (KRaft or ZooKeeper)
- Redpanda
- Confluent Platform
连接方式
您需要准备
- SASL/PLAINFor a SASL_SSL listener only: the password is accepted over TLS and never sent in clear text.
无需账户。
需要开放的网络端口
9092/TCPKafka protocol (default port, plain or TLS), every broker is contacted
设置步骤: Give DumbMonit read-only access to Kafka
Skip this step for a cluster without an authorizer. Otherwise give a dedicated principal read-only ACLs, from a host that can reach the brokers.
kafka-acls.sh --bootstrap-server kafka.lan:9092 --add --allow-principal User:dumbmonit --operation Describe --cluster kafka-acls.sh --bootstrap-server kafka.lan:9092 --add --allow-principal User:dumbmonit --operation Describe --topic '*' kafka-acls.sh --bootstrap-server kafka.lan:9092 --add --allow-principal User:dumbmonit --operation Describe --group '*'In DumbMonit, enter the address of one broker, for example kafka.lan:9092: DumbMonit then contacts the other brokers at the addresses they advertise.
Tick TLS if the listener is SSL or SASL_SSL, and enter the SASL/PLAIN user and password if the listener asks for them.
注意. Each broker must be reachable at the address it advertises (advertised.listeners): a broker DumbMonit cannot reach leaves the consumer lag incomplete. SASL/PLAIN is accepted only over TLS; SCRAM and Kerberos are not supported.