kafka-monitor icon indicating copy to clipboard operation
kafka-monitor copied to clipboard

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 availab...

Results 35 kafka-monitor issues
Sort by recently updated
recently updated
newest added

Issue. #395 This PR aims to provide parallel Producer per partition, so that even if one partition is slow(hosted on slow Brtoker) other producers can easily produce data on other...

This is something we saw in our Production Kafka Cluster. There was one Slow Broker in Kafka Cluster, and KMF was struggling to Produce Data on the partition hosted on...

As shown in the conversations https://linkedin-randd.slack.com/archives/C04FMP0HB17/p1671222219329569, if a new monitoring topic is just created in a cluster, the AdminClient.describeTopic API could result in UnknownTopicOrPartitionExceptions, which causes the whole process to...

Xinfra monitor [has recently been upgraded to version 2.8 of kafka client libraries](https://github.com/linkedin/kafka-monitor/pull/378), where adminClient does not use zookeeper dependency anymore. This gives a great opportunity to remove all zookeeper...

Hello, I have deployed kafka-monitor on our cluster. Helm deployment was successful but to container is in CrashLoopBackOff state. Logs from pod: Exception in thread "main" com.fasterxml.jackson.core.JsonParseException: Unexpected character ('}'...