Hello Andrew, I’m reminded of the client.id discussion we had back in KIP-1313 re: client instance id. After that discussion, I have a WIP KIP that sets a foundation for shipping client metadata tags to be sent for telemetry. I was hoping we could discuss if part of that approach could fit this KIP.
AK1. I had a note on the motivation of selecting a “framework” as a blessed abstraction. The KIP mentions it’s for the client metadata and easier problem diagnosis. This is akin to an “application id” that non-framework clients usually tag with. KIP-606 took an approach like metrics.context.<key>=<val>. If we allow client.metadata.<key>=<val>, then a framework/application name and version can sit in such a metadata context and be sent with ApiVersion RPC. Of course, this is an open box approach rather than just the framework name/version (just two fields) we’re adding to the protocol. But I’m curious about the tier of importance of framework alone. AK2. Can you clarify if this config goes into CommonClientConfigs.java, referenced across producer/consumer/share etc? I know some share props have the “share.” prefix going. AK3. In another thread you mentioned that the broker may add it to the request context. In client logs, clientId is a very useful string to identify WARN logs when things go sideways like broker disconnected, rebalance in progress etc. Can you cherry pick and highlight some useful log places that these strings can go? I suppose adding clientId/framework to the MDC context might be too voluminous. AK4. I foresee collectors like Datadog/OTel might find these tags useful in each span exported. Looking forward to your thoughts on this. Regards, Aditya > On Jul 17, 2026, at 11:53, Andrew Schofield > <[email protected]> wrote: > > Hi, > I'd like to open discussion on KIP-1368: Client framework name and version. > > Applications often use application frameworks such as Spring to connect to > Kafka. To assist with problem diagnosis, this KIP introduces a way to provide > the framework name and version as part of the metadata the client sends to > the broker when it connects. > > Here's the KIP: https://cwiki.apache.org/confluence/x/J4Q_Gg > > Thanks, > Andrew
