DumbMonit
ИнтеграцииБазы данных и очереди сообщений
Мониторинг Apache Kafka в DumbMonit
The event streaming cluster: offline and under-replicated partitions, a missing controller, and the lag of the consumer groups.
ДокументацияОфициальный сайт: Apache Kafka
Описания на английском, как в самом продукте. Подписи на странице — на вашем языке.
Что проверяет 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.