Finding all groups, then getting the topic from those groups is the only way to get that information.
The standard use case is to find lag by an application (group.id). There's little user benefit to finding the lag of all applications (groups) consuming from one topic, and this is more of an administrative feature, thus be better suited to use Burrow or other lag collection utilities that can aggregate such metrics
If the use case is to find all client addresses consuming from that topic, then there's no good data lineage product that I'm aware of outside Cloudera SMM tool
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…