wrote:
> >
> > > Should state I have no objections adding this client side, just more a
> > > question to why we don't look and propose to add this broker side also.
> > >
> > > Sent using OWA for iPhone
> > > ____
; question to why we don't look and propose to add this broker side also.
> >
> > Sent using OWA for iPhone
> >
> > From: Michael Pearce <michael.pea...@ig.com>
> > Sent: Monday, November 14, 2016 4:58:45 PM
> >
gt; From: Michael Pearce <michael.pea...@ig.com>
> Sent: Monday, November 14, 2016 4:58:45 PM
> To: dev@kafka.apache.org
> Subject: Re: [DISCUSS] KIP-92 - Add per partition lag metrics to
> KafkaConsumer
>
> Why do we not look to expose the lag broker side centrally?
>
:58:45 PM
To: dev@kafka.apache.org
Subject: Re: [DISCUSS] KIP-92 - Add per partition lag metrics to KafkaConsumer
Why do we not look to expose the lag broker side centrally?
Eg like burrow.
>From an operations point it's a lot easier to monitor lag centrally than per
>application. Als
fka based or zookeeper offsets is
available to the broker.
From: Becket Qin <becket@gmail.com>
Sent: Sunday, November 13, 2016 4:13:01 AM
To: dev@kafka.apache.org
Subject: [DISCUSS] KIP-92 - Add per partition lag metrics to KafkaConsumer
Hi,
We
Hi,
We created KIP-92 to propose adding per partition lag metrics to
KafkaConsumer.
The KIP wiki link is the following:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-92+-+Add+per+partition+lag+metrics+to+KafkaConsumer
Comments are welcome.
Thanks,
Jiangjie (Becket) Qin
