Related, it seems like the logback project might be dead? There are 79 open PRs (https://github.com/qos-ch/logback/pulls) and no commits since May. Furthermore, the Travis build is currently failing on master.
I did a spike of adding MDC to logback-access, but I'm worried about the ability to get it merged. I'm really interested if people have other ways of logging per-request values along with the jetty access log. Thanks, Paul On Tue, Nov 1, 2016 at 2:29 PM, Paul Gross <[email protected]> wrote: > We are currently upgrading our dropwizard app from 0.9.3 to 1.0.2. One of > the things that is currently biting us is the move to logback-access. It > looks like logback-access does not support MDC[1], so we can't include > per-request values with our log lines. For example, we set a unique id per > request in the MDC, and then include this with every log line. Is this > possible a different way now with logback-access? > > Concretely, there's a shift from ILoggingEvent to IAccessEvent for these > messages (described in the PR[2]), and IAccessEvent does not include the > MDC map like ILoggingEvent[3]. > > Thanks, > Paul > > [1] http://jira.qos.ch/browse/LOGBACK-1016 > [2] https://github.com/dropwizard/dropwizard/pull/1415# > issuecomment-174312359 > [3] https://github.com/qos-ch/logback/blob/03e26684d43066d53dbf926e060a73 > d43bee77fd/logback-classic/src/main/java/ch/qos/logback/ > classic/spi/ILoggingEvent.java#L75 > > -- You received this message because you are subscribed to the Google Groups "dropwizard-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
