Hi everyone, I'd like to propose a new FLIP that builds directly on the excellent foundation laid by FLIP-481 (Introduce Event Reporting). For anyone needing context, the original proposal is available here: https://cwiki.apache.org/confluence/display/FLINK/FLIP-481%3A+Introduce+Event+Reporting
Now that the community has this powerful API, the logical next step is to ensure it's fully robust for large-scale production environments where users will be writing their own diverse, custom reporters. This proposal focuses on one key enhancement: introducing a resilient, asynchronous dispatch core. The goal is to decouple event generation from the reporter's execution, ensuring that a slow or experimental sink can never impact Flink's core stability. I've drafted a detailed design document that I hope can form the basis of this new FLIP: https://docs.google.com/document/d/1CCu7Js0ATOAgqRMS-kWj_0v0G_jt2r9IfMB2Oty7KJo/edit?usp=sharing I'm keen to get the community's initial feedback on this direction before moving forward with the formal process. Thanks, Kartikey Pant
