Hi everyone! I wanted to ask how we can raise and log run-time exceptions in the terminal. We use Flink for live data streaming and aggregation - we apply Flink SQL to initiate our tables and perform our aggregate join query and then execute them using executeSql(String query). Since data streaming is new for us, we are unaware on how we can enable further telemetry. What do you recommend we do for logging exceptions? In our minds, we were thinking of placing a try-catch block around the executeSql() but unsure on what exceptions to expect and how they would behave in run-time.

Why do you need to put a try block around executeSQL? The job manager will restart the job if it fails. Exceptions are already logged. You would monitor the process as you would with any other application (like a web server). You can aggregate log files into something like Splunk, etc... You can use Grafana or other observability tools like with any other application. Maybe I'm missing something about your question.

I would recommend looking through the log configuration documentation where you can configure log levels for the various classes