-
Notifications
You must be signed in to change notification settings - Fork 443
App Overview
The most flexible way to start kafka-monitor is to run kafka-monitor-start.sh with a config file, which allows you to instantiate multiple Service or App that are already implemented in Kafka Monitor and tune their configs to monitor your clusters. An App is typically composed of multiple Service classes to carry out a more complicated task, e.g. produce message and verify that the message can be consumed.
In this section we introduce some App classes that have been implemented in Kafka Monitor. See App Configuration for their configs.
SingleClusterMonitor is useful to monitor the availability of a given cluster. It is composed of one ProduceService and one ConsumeService to verify that the messages produced by ProduceService can be consumed by ConsumeService in order and without messsage loss. All JMX metrics exposed by ProduceService and ConsumeService will be exposed by SingleClusterMonitor as well.
Xinfra Monitor (KMF): https://github.com/linkedin/kafka-monitor/
For inquiries or issues: https://github.com/linkedin/kafka-monitor/issues/new