Thanks for the comments! I will open the voting thread later today!.
Best,
Piotrek
śr., 4 gru 2024 o 22:56 Roman Khachatryan napisał(a):
> Thanks for updating the FLIP and clarifying.
>
> > That might have been a good idea, however this is consistent with the
> ? already pre-existing traces/`Sp
Thanks for updating the FLIP and clarifying.
> That might have been a good idea, however this is consistent with the
? already pre-existing traces/`SpanBuilder`.
> I'm not sure what you would propose in this context? Make those two places
> inconsistent?
Good point, I think consistency is more im
Hi Roman!
> 1. Should it list the events that would be emitted in the first version?
> If not as part of the proposed change, then maybe as examples
I've added a brief list of events that will be added in the first version.
> 2. Interface Event - Scope
> It's scope is explicitly tied to a Class
Hi Piotr, thanks for the proposal!
I think this would be a very valuable addition to Flink as it would
simplify operations a lot
(disclaimer: we already use it in our internal Flink version)
I have a couple of remarks regarding the FLIP:
1. Should it list the events that would be emitted in the
Hi all!
I would like to open up for the discussion a new FLIP [1]
Motivation
Currently, Flink observability has support for Metrics and Traces. We
suggest enhancing the observability capabilities by adding support for
Events. This can be used to track the most important events that happen in
Fli
