Page History

...

Several options were proposed in https://issues.apache.org/jira/browse/KAFKA-5061:

"Provide default client IDs based on the worker group ID + task ID (providing uniqueness for multiple connect clusters up to the scope of the Kafka cluster they are operating on)"
This is the same as the proposed approach, but with unique.client.id always set to true. It avoids an external interface
 This option avoids a configuration change, but does not maintain backward compatibility and will alter metrics names in existing clusters that have not explicitly overridden the client id in configuration.  NOTE: This would be the simplest option if backwards compatibility is not a serious concern.  A possible implementation is offered in this PR:  https://github.com/apache/kafka/pull/6097

"Allow overriding client.id on a per-connector basis"

This would not allow for per-task monitoring, as all tasks created by a connector would share the same client id.  A related option is to offer connectors more direct control of the client id, in configuration or code.  This would require a much more complex change, and would require individual connectors to be updated to support the change. In contrast, the proposed approach would immediately allow detailed consumer/producer monitoring for all existing connectors.