[
https://issues.apache.org/jira/browse/KAFKA-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649280#comment-15649280
]
Ewen Cheslack-Postava commented on KAFKA-4381:
----------------------------------------------
Yeah, I don't want things to get bogged down in KIPs either. I just figure
following the rule of "any public interface" makes it easy for everyone to know
whether they need a KIP or not (e.g. monitoring is listed on the KIP page since
they are user facing). We definitely play fast and loose with this elsewhere
anyway though, e.g. command line tools often see user facing changes w/o KIPs,
and most of them will be uncontroversial anyway. On the other hand, I've caught
important backwards incompatible changes that almost made it through as well,
so...
> 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)
