Hi Andrew, Thanks for taking a look! Yeah after experimenting with the approach now listed in the rejected alternatives, I thought it was better to just bring whole new interfaces.
AS1: I was following the naming from ClientTelemetry, but I agree it's probably simpler to name that method clientTelemetryExporter(). I've updated the KIP. Thanks, Mickael On Wed, Sep 10, 2025 at 4:26 PM Andrew Schofield <[email protected]> wrote: > > Hi Mickael, > Thanks for the KIP. It looks like a nice improvement. > > I previously read an earlier version and had some comments, but > you've already addressed them and added to the rejected alternatives :) > Just one additional comment. > > AS1: I suggest the method in the ClientTelemetryExporterProvider > interface would be better named clientTelemetryExporter. > > Thanks, > Andrew > > ________________________________________ > From: Mickael Maison <[email protected]> > Sent: 09 September 2025 16:56 > To: dev <[email protected]> > Subject: [DISCUSS] KIP-1217: Include push interval in ClientTelemetryReceiver > context > > Apologies, the KIP number is 1217: > KIP-1217: Include push interval in ClientTelemetryReceiver context: > https://cwiki.apache.org/confluence/x/6QnxFg > > On Tue, Sep 9, 2025 at 5:52 PM Mickael Maison <[email protected]> > wrote: > > > > Hi, > > > > I'd like to start a discussion on KIP-1127: > > https://cwiki.apache.org/confluence/x/6QnxFg > > > > This small KIP proposes providing the push interval to > > ClientTelemetryReceiver implementations to improve the management of > > client telemetry metrics. > > > > Thanks, > > Mickael
