Hi, Andrew, Thanks for the KIP. A few comments.
JR1. Currently, you can configure a client quota based on clientId. Currently, the broker extracts the clientId from the request header. If clientId is not included in every request, can we document where the server will obtain it? JR2. client instance ID: JR2.1 Is it only sent on the first request in a connection? If so, have we considered making it part of the ApiVersionRequest instead of the request header? JR2.2 It would be useful to include the client instance ID in request logging on the server side. Could we document how to make that available for each request the server processes? JR3. "The client instance ID will be calculated during the constructor of the Producer , Consumer and Admin". What about ShareConsumer? JR4. GetTelemetrySubscriptions: Could we document the changes in the response too? Jun On Fri, Apr 3, 2026 at 9:18 AM Andrew Schofield <[email protected]> wrote: > Hi, > I would like to start the discussion on KIP-1313. This adds a unique > client instance ID to the request header of all Kafka protocol requests to > give a unique identifier which can be used to correlate the requests from > each client for the purposes of problem determination. > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1313%3A+Client+instance+ID+in+all+request+headers > > Thanks, > Andrew >
