Hi, no, but I am using a custom ch.qos.logback.classic.spi.Configurator and doing everything manually. Largely this is because I got a bit fed up with every project having a different logging setup and badly managed XML files. So most of our Java projects use the same Configurator that ensures we have consistent logging. I also pick up env vars and adjust the log levels based on them (and have a web endpoint that can report and change log levels on the fly, https://github.com/Yaytay/vertx-management-endpoints#logbackmgmtroute). On Kubernetes installations it outputs in Json using logstash-logback-encoder, but that is incompatible with a change in 1.X.8 (https://github.com/logfellow/logstash-logback-encoder/pull/976) so I'm looking at replacing with the new native Json output. The logstash encoder includes additional context data that I need to get into the MDC for the Json encoder (mainly distributed tracing span/trace IDs). |