Hi Vahid, Thanks for the response.
Kafka currently has a partition leader count metric per broker. The total partition count metric can be built by summing the partition leader count across the cluster. This information may not be consistent but it'll be eventually consistent in steady state. But if you think it'll be useful to add this metric in relation with the offline partition count to track them in tandem, then I guess it might be useful. Also, this will be consistent as it is coming from the controller. Let me know your thoughts on this. Best, Abhishek On Wed, Jun 28, 2017 at 9:05 AM, Vahid S Hashemian < vahidhashem...@us.ibm.com> wrote: > Hi Abhishek, > > Thanks for the KIP and sorry for posting late on this thread. > > The proposal looks good to me. > I wonder if it would be useful to also add a partition count metric. > It seems there is already an offline partition count metric in the > controller, but no total partition count. > > Thanks. > --Vahid > > > > From: Abhishek Mendhekar <abhishek.mendhe...@gmail.com> > To: dev@kafka.apache.org > Date: 06/16/2017 09:09 AM > Subject: [DISCUSS] KIP-168: Add TotalTopicCount metric per cluster > > > > Hi Kafka Dev, > > I created KIP-168 to propose adding a metric to emit total topic count > in a cluster. The metric will be emited by the controller. > > The KIP can be found here > ( > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 168%3A+Add+TotalTopicCount+metric+per+cluster > ) > and the assciated JIRA improvement is KAFKA-5461 > (https://issues.apache.org/jira/browse/KAFKA-5461) > > Appreciate all the comments. > > Best, > > Abhishek > > > > > -- Abhishek Mendhekar abhishek.mendhe...@gmail.com | 818.263.7030
