[
https://issues.apache.org/jira/browse/KAFKA-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16866189#comment-16866189
]
Boyang Chen commented on KAFKA-3556:
------------------------------------
[~guozhang] Sounds good, I found the rebalance duration/latency for each
individual group pretty useful, because it's easier to monitor in a centralized
location for the entire group status.
Also, in terms of join/sync round trip latency, I wonder if we should focus on
server side latency instead of client, because under current semantic, the time
needed to propagate from stable to prepare rebalance and then to complete
rebalance should be the dominant factor for round trip latency on client side.
> 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
> Priority: Major
>
> 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
(v7.6.3#76005)
