[
https://issues.apache.org/jira/browse/KAFKA-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15645419#comment-15645419
]
Joel Koshy commented on KAFKA-4381:
-----------------------------------
This is up to you but I definitely agree with Jason that it's overkill to have
KIPs for this level of improvement. Configs are similar as well unless they are
very nuanced such as timeouts. The PR itself should be sufficient to serve as a
forum to discuss any concerns.
Metric name changes are different since presumably people are already
monitoring those metrics - such changes could deserve a KIP or even just a
email heads-up.
> Add per partition lag metric to KafkaConsumer.
> ----------------------------------------------
>
> Key: KAFKA-4381
> URL: https://issues.apache.org/jira/browse/KAFKA-4381
> Project: Kafka
> Issue Type: Task
> Components: clients, consumer
> Affects Versions: 0.10.1.0
> Reporter: Jiangjie Qin
> Assignee: Jiangjie Qin
> Fix For: 0.10.2.0
>
>
> Currently KafkaConsumer only has a metric of max lag across all the
> partitions. It would be useful to know per partition lag as well.
> I remember there was a ticket created before but did not find it. So I am
> creating this ticket.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
