Hi Dhruv,
Yes, the AsyncSink might be a good fit to implement your use case. In
general, the AsyncSink is meant to be used for writing to external
systems that do not support native transactions and can therefore not
guarantee exactly-once semantics. As a starting point, you can look at
the existi
cc user@, bcc dev@
Hi Dhruv,
Yes, this should be totally possible.
For 1, I would use a ProcessFunction to buffer the alerts and register
timers per alert for the repeated firing (or to clear it from state if it
is resolved). From this ProcessFunction you send records to an
AlertManagerSink.
Fo
