Xinfra Monitor monitors the availability of Kafka clusters by producing synthetic workloads using end-to-end pipelines to obtain derived vital statistics - E2E latency, service produce/consume availability, offsets commit availability & latency, message loss rate and more.
I'd like to use MultiClusterMonitor for monitor Kafka async cluster with MirrorMaker 2. As you know MM2 creates topic with source prefix on destination cluster, but I guess Kafka-monitor does not get it, and tries to consume topic without prefix.
Maybe there is directive in config file that makes it consume prefixed topic?
Does MultiClusterMonitor app supports MirrorMaker2?
Hello!
I'd like to use MultiClusterMonitor for monitor Kafka async cluster with MirrorMaker 2. As you know MM2 creates topic with source prefix on destination cluster, but I guess Kafka-monitor does not get it, and tries to consume topic without prefix. Maybe there is directive in config file that makes it consume prefixed topic? Does MultiClusterMonitor app supports MirrorMaker2?