Hi Kirk, thanks for the KIP. This is definitely a gap that we encounter on a daily basis.
After reading the KIP I have a few questions: 1. Would it be possible to enforce configuration policies by rejecting configurations that the cluster operators deem invalid. An example that comes to mind is setting acks=0 (or 1) 2. In the same vein, how about overwriting client configurations? So, instead of rejecting configurations, operators could enforce certain configuration values (acks=-1, linger.ms >= N ms, etc.) 3. If the goal of the KIP is just to collect data, have you thought about extending KIP-714 and just publish the new configurations as new standard metrics? Most of the configurations listed on the KIP have either scalar values or enums (which could be translated to scalars). Cheers, From: [email protected] At: 04/23/26 13:59:52 UTC-4:00To: [email protected] Subject: [DISCUSS] KIP-1324: Support client configuration observability Hi all, I would like to start a discussion on KIP-1324: Support client configuration observability: https://cwiki.apache.org/confluence/display/KAFKA/KIP-1324%3A+Support+client+con figuration+observability Thanks, Kirk
