on the client-side auditor/interceptor/observer
> > > (sorry
> > > > > about the potential confusion caused by these words being used
> > > > > interchangeably).
> > > > >
> > > > > Best regards,
> > > > > Linco
; > > > On Wed, Dec 4, 2019 at 8:15 AM Thomas Aley
> > wrote:
> > > >
> > > > > Thanks for the responses. I did worry about the challenge of
> > exposing a
> > > > > vast number of internal classes with general interceptor
> framework. A
&
t; > Thanks for the responses. I did worry about the challenge of
> exposing a
> > > > vast number of internal classes with general interceptor framework. A
> > > less
> > > > general solution more along the lines of the producer/consumer
> > > > interceptors on the
come up with a pattern that could be
> > > extended further in future if the community sees the demand.
> > >
> > > Looking through the discussion thread for KIP-388, I see a lot of good
> > > points to consider and I intend to dive further into this.
tend to dive further into this.
> >
> >
> > Tom Aley
> > thomas.a...@ibm.com
> >
> >
> >
> > From: Ismael Juma
> > To: Kafka Users
> > Cc: dev
> > Date: 03/12/2019 16:12
> > Subject:[EXTERNAL] Re: Broker I
ey
> thomas.a...@ibm.com
>
>
>
> From: Ismael Juma
> To: Kafka Users
> Cc: dev
> Date: 03/12/2019 16:12
> Subject:[EXTERNAL] Re: Broker Interceptors
>
>
>
> The main challenge is doing this without exposing a bunch of internal
> classes
: Ismael Juma
To: Kafka Users
Cc: dev
Date: 03/12/2019 16:12
Subject:[EXTERNAL] Re: Broker Interceptors
The main challenge is doing this without exposing a bunch of internal
classes. I haven't seen a proposal that handles that aspect well so far.
Ismael
On Tue, Dec 3, 2019 at 7:21
ceptors - the capability exists and it is an opt-in feature.
> > > >
> > > > As with the client interceptors and indeed interception in general, the
> > > > interceptor implementations need to be thoughtfully crafted to ensure
> > > > minimal performance
n feature.
> > >
> > > As with the client interceptors and indeed interception in general, the
> > > interceptor implementations need to be thoughtfully crafted to ensure
> > > minimal performance impact. Yes the interceptor framework could tap
> into
> > >
ted to ensure
> > minimal performance impact. Yes the interceptor framework could tap into
> > nearly everything but would only be tapping into the subset of APIs that
> > the user wishes to intercept for their use case.
> >
> > Tom Aley
> > thomas.a...@ibm.com
>
early everything but would only be tapping into the subset of APIs that
> the user wishes to intercept for their use case.
>
> Tom Aley
> thomas.a...@ibm.com
>
>
>
> From: "M. Manna"
> To: Kafka Users
> Cc: d...@kafka.apache.org
> Date: 02/12/20
to intercept for their use case.
Tom Aley
thomas.a...@ibm.com
From: "M. Manna"
To: Kafka Users
Cc: d...@kafka.apache.org
Date: 02/12/2019 11:31
Subject:[EXTERNAL] Re: Broker Interceptors
Hi Tom,
On Mon, 2 Dec 2019 at 09:41, Thomas Aley wrote:
> Hi Kafka commun
Hi Tom,
On Mon, 2 Dec 2019 at 09:41, Thomas Aley wrote:
> Hi Kafka community,
>
> I am hoping to get some feedback and thoughts about broker interceptors.
>
> KIP-42 Added Producer and Consumer interceptors which have provided Kafka
> users the ability to collect client side
Hi Kafka community,
I am hoping to get some feedback and thoughts about broker interceptors.
KIP-42 Added Producer and Consumer interceptors which have provided Kafka
users the ability to collect client side metrics and trace the path of
individual messages end-to-end.
This KIP also mentioned
14 matches
Mail list logo
