Hi Kevin,
I haven't worked with Bugsnag. So, I cannot give more input on that one.
For Flink, exceptions are handled by the job's scheduler. Flink collects
these exceptions in some bounded queue called the exception history [1]. It
collects task failures but also global failures which make the job
Are you only interested in exceptions that result in the job failing? If
so, then https://issues.apache.org/jira/browse/FLINK-20833 may be of
interest to you.
On 6/18/2021 5:15 PM, Kevin Lam wrote:
Hi all,
I'm interested in instrumenting an Apache Flink application so that we
can monitor exc
Hi all,
I'm interested in instrumenting an Apache Flink application so that we can
monitor exceptions. I was wondering what the best practices are here? Is
there a good way to observe all the exceptions inside of a Flink
application, including Flink internals?
We are currently thinking of using B
Hi all,
I'm interested in instrumenting an Apache Flink application so that we can
monitor exceptions. I was wondering what the best practices are here? Is
there a good way to observe all the exceptions inside of a Flink
application, including Flink internals?
We are currently thinking of using B
