...

So, for example, if you run two MirrorSourceConnector tasks, the "kafka.connect.mirror:type=kafka-metrics-count" metric is shown as 13, even though there are actually 26 metrics, 13 for each task.

This KIP proposes providing the tags, connector name and task index, to each task, so that MirrorMaker tasks' metrics can be reported per task.

Additionally, Furthermore, "kafka.connect.mirror:type=kafka-metrics-count" metric is created without any tags, unlike other task metrics, leading to collisions. Even with the connector name and task index added, it was still insufficient. To ensure kafka-metrics-count is displayed correctly, this KIP changes the source and target as default tags when creating the Metrics instance. Otherwise, using only the connector name and task index can still lead to collisions; for example, if there are two clusters, A and B: Cluster A → B creates its own Metrics instance, and Cluster B → A creates its own as well.

This KIP proposes providing the tags (connector name and task index), and setting the source and target as default tags when creating the Metrics instance for each task, so that MirrorMaker task metrics can be reported per task without collisions.

Public Interfaces

1) A new configuration setting for MirrorSourceConnector and MirrorCheckpointConnector in MirrorConnectorConfig:

...