On the second thought, If you are already managing to pass the value using the request parameters, what stops you from just having a servlet filter looking for that parameter and assigning it directly to the MDC context?
Regards, Alex. Personal website: http://www.outerthoughts.com/ Current project: http://www.solr-start.com/ - Accelerating your Solr proficiency On Sat, Apr 5, 2014 at 7:45 AM, Alexandre Rafalovitch <arafa...@gmail.com> wrote: > I like the idea. No comments about implementation, leave it to others. > > But if it is done, maybe somebody very familiar with logging can also > review Solr's current logging config. I suspect it is not optimized > for troubleshooting at this point. > > Regards, > Alex. > Personal website: http://www.outerthoughts.com/ > Current project: http://www.solr-start.com/ - Accelerating your Solr > proficiency > > > On Sat, Apr 5, 2014 at 3:16 AM, Gregg Donovan <gregg...@gmail.com> wrote: >> We have some metadata -- e.g. a request UUID -- that we log to every log >> line using Log4J's MDC [1]. The UUID logging allows us to connect any log >> lines we have for a given request across servers. Sort of like Zipkin [2]. >> >> Currently we're using EmbeddedSolrServer without sharding, so adding the >> UUID is fairly simple, since everything is in one process and one thread. >> But, we're testing a sharded HTTP implementation and running into some >> difficulties getting this data passed around in a way that lets us trace >> all log lines generated by a request to its UUID. >>
