Hi Kartikey, +1 Thanks for the FLIP. This is going to improve a key part of observability for flink which would open further avenues as mentioned in the FLIP.
Regards, Nishita Pattanayak On Wed, 2 Jul 2025 at 1:32 PM, Kartikey Pant <kartikeypant....@gmail.com> wrote: > Hi Flink Devs, > > Following up on this thread from May. Thank you again, Li Wang, for the > helpful initial discussion. > > I have now completed a full revision of the Events Reporter System > proposal. From my side, the FLIP is complete and ready for a full community > review. > > The document is here: > > https://docs.google.com/document/d/1R4fmOTQDLZcUQwgmCCxoRb74MGPZOypiScUbKL43AL4 > > My goal is to gather feedback to move towards community consensus and a > formal vote. > > I would greatly appreciate your time and review. > > Best regards, > > Kartikey Pant > > On Tue, May 27, 2025 at 6:47 PM Kartikey Pant <kartikeypant....@gmail.com> > wrote: > > > Hi Li, > > > > Thanks for the positive feedback on the FLIP! I appreciate you taking the > > time. Glad you see the potential, especially for autonomous operations - > > it's a key driver. > > > > Your question on the Kafka reporter is great; it'll be a vital > > implementation. V1's core goal is to establish the right foundation, > making > > it safer to build these reporters later. > > > > Here’s how V1 enables it: > > 1. EventsReporter Interface: The main extension point; a Kafka reporter > > implements open, reportEvent, and close. > > 2. Async Dispatch: A local EventDispatchService decouples via its > > queue/thread. Flink uses a non-blocking offer() so slow reporters won't > > block the JobManager. If full, V1 logs/drops, prioritizing stability. > > 3. Config & Data: Standard flink-conf.yaml pattern. V1 defines the > > FlinkOperationalEvent (JSON) for consistency. > > > > V1 provides the stable framework so future devs can focus on Kafka logic. > > This enables secure additions and supports our AIOps goals. Building a > > production Kafka reporter still involves design choices (producer > settings, > > backpressure, schemas). > > > > With that in mind, I'd be interested to hear community thoughts: What are > > critical features/challenges for a KafkaEventsReporter? E.g., delivery > > guarantees vs. stability? Getting perspectives now is valuable. Based on > > this feedback, I'm happy to update the FLIP to include these > considerations > > for V2+. > > > > Thanks again for the discussion! > > > > Best regards, > > Kartikey Pant > > >
