A web-based tool for managing Apache Kafka clusters, enabling cluster inspection, topic management, and partition operations.
CMAK (Cluster Manager for Apache Kafka) is a comprehensive web-based tool for managing Apache Kafka clusters. It provides administrators with an intuitive interface to monitor cluster health, manage topics and partitions, and perform essential maintenance operations without relying on command-line tools.
Kafka administrators, DevOps engineers, and platform teams responsible for operating and maintaining Apache Kafka clusters in production environments.
Developers choose CMAK for its user-friendly web interface that simplifies complex Kafka cluster administration, supports multi-cluster management from a single dashboard, and offers extensive features like JMX polling and consumer tracking that reduce reliance on CLI tools.
CMAK is a tool for managing Apache Kafka clusters
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Allows managing multiple Kafka clusters from a single web interface, simplifying administration for distributed environments as highlighted in the features list.
Supports full CRUD operations on topics, including config updates and partition reassignments, directly from the UI without CLI reliance.
Tracks consumer groups and offsets, even those not stored in ZooKeeper, providing visibility into consumer lag and filtering options.
Optional JMX polling enables broker-level and topic-level metrics visualization, reducing the need for separate monitoring tools.
Only compatible with Kafka up to 0.11.*.*, missing support for newer features and security enhancements in recent releases, which limits its use in modern stacks.
For large clusters, administrators must manually configure thread pools and queue sizes in application.conf, as detailed in the README, which can be error-prone and time-consuming.
The KafkaManagedOffsetCache uses a single thread per cluster and is untested with large numbers of offsets, potentially causing bottlenecks and unreliable lag reporting.
LDAP authentication requires SSL configuration and has numerous parameters, making initial setup and maintenance challenging, with warnings about insecure credentials without encryption.