You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Liquan Pei (JIRA)" <ji...@apache.org> on 2016/04/22 07:37:12 UTC

[jira] [Assigned] (KAFKA-3556) Improve group coordinator metrics

     [ https://issues.apache.org/jira/browse/KAFKA-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Liquan Pei reassigned KAFKA-3556:
---------------------------------

    Assignee: Liquan Pei

> Improve group coordinator metrics
> ---------------------------------
>
>                 Key: KAFKA-3556
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3556
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Jason Gustafson
>            Assignee: Liquan Pei
>
> We currently don't have many metrics to track the behavior of the group coordinator (especially with respect to the new consumer). On a quick pass, I only saw a couple gauges in GroupMetadataManager for the number of groups and the number of cached offsets. Here are some interesting metrics that may be worth tracking:
> 1. Session timeout rate
> 2. Rebalance latency/rate
> 3. Commit latency/rate
> 4. Average group size
> 5. Size of metadata cache
> Some of these may also be interesting to track per group.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)