Answering our own question. >From what we can see, all you need to do is tweak the /usr/lib/flink/conf and /usr/lib/flink/lib directories so that you remove the log4j.properties and have your logback.xml in conf and the required libraries in the lib directory (removing the log4j backend in place of logback). Then when you launch your flink jobs they will be clones with the correct files and happy as larry!
Haven't figured out how to handle for ephemeral EMR clusters... but we aren't using them so :shrug: On Wed, 4 Sep 2019 at 22:17, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Has anyone configured AWS EMR’s flavour of Flink to use Logback (more > specifically with the logstash encoder, which would require additional jars > on the classpath) > > Or is there an alternative way people are using to send the logs to a > service like Datadog > > Thanks in advance > > Stephen > -- > Sent from my phone >