de, just more a
> > > question to why we don't look and propose to add this broker side also.
> > >
> > > Sent using OWA for iPhone
> > > ____
> > > From: Michael Pearce
> > > Sent: Monday, N
n't look and propose to add this broker side also.
> >
> > Sent using OWA for iPhone
> >
> > From: Michael Pearce
> > Sent: Monday, November 14, 2016 4:58:45 PM
> > To: dev@kafka.apache.org
> > Subject: Re: [DISCUSS] KIP-92 - Add per pa
Pearce
> 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?
>
> Eg like burrow.
>
> From an operations point
: 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. Also then you'd
uses Kafka based or zookeeper offsets is
available to the broker.
From: Becket Qin
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 created KIP-92 to
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
