Hi Mickael, Thanks for the KIP! While reviewing 877 I remember wondering if/when we'd see this follow-up. I think it's a good idea to align the MM2 metrics with the 877 style and eat some of our own dogfood as well. Thoughts:
1. Can we support a dual-write mode to reduce risk during upgrades? Can elaborate more on the motivation here if necessary. 2. I take it the heartbeat connector and client utils don't report any custom metrics? If so, would be nice to see that called out, and if not, I'd expect to see them mentioned in either a rejected alternatives or future work section. 3. Guessing we'll want to log some kind of notice to users who are still using the legacy metrics? I don't care (at this point) whether it's at info or warn level but it'd be nice to know that we plan to emit some kind of message. 4. (Nit) I think the "Update Mode" attribute for the new property may have been left in accidentally? If not, would you mind explaining what it means for a connector? Cheers, Chris On Fri, Feb 13, 2026, 11:19 Mickael Maison <[email protected]> wrote: > Hi, > > I'd like to start a discussion about KIP-1280: > https://cwiki.apache.org/confluence/x/a4s8G > > This proposes updating the MirrorMaker connectors to use KIP-877 to > register their metrics. > > Let me know if you have any questions or feedback. > > Thanks, > Mickael >
