This PR separates the Kafka and Yammer specific metric logic. This ensures that when usingKafkaPrometheusMetricsReporter, only classes present in kafka-clients are used. On the other hand YammerPrometheusMetricsReporter can use all dependencies present in the Kafka distribution as it's only used on the server side.
@mimaison could you add a sentence or two to the PR description outlining at a high level how the problem is solved. It should help reviewers understand the intent.
This fixes #48
This PR separates the Kafka and Yammer specific metric logic. This ensures that when using
KafkaPrometheusMetricsReporter
, only classes present in kafka-clients are used. On the other handYammerPrometheusMetricsReporter
can use all dependencies present in the Kafka distribution as it's only used on the server side.