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.
Hello team, I faced the issue with cluster-topic-manipulation-service it doesn't work for me at all.
So when I'm configuring this it doesn't create a topic for iterations and didn't send any info into "reporter-service" and to "statsd-service" metrics accordingly. However, the other configuration works as it should. Could you please check my config file, maybe I made some mistakes:
In addition, I have a question, is it possible that the "cluster-topic-manipulation-service" would work with Kafka brokers only, without zookeepers? This is very important for our infrastructure.
Also, I noticed that there is no possibility to reload service configuration without application restart. Our case is necessary for pkcs12 Keystore reloading every 24 hours. Could you please add this possibility in future releases?
Hello team, I faced the issue with cluster-topic-manipulation-service it doesn't work for me at all. So when I'm configuring this it doesn't create a topic for iterations and didn't send any info into "reporter-service" and to "statsd-service" metrics accordingly. However, the other configuration works as it should. Could you please check my config file, maybe I made some mistakes:
In addition, I have a question, is it possible that the "cluster-topic-manipulation-service" would work with Kafka brokers only, without zookeepers? This is very important for our infrastructure. Also, I noticed that there is no possibility to reload service configuration without application restart. Our case is necessary for pkcs12 Keystore reloading every 24 hours. Could you please add this possibility in future releases?