ODL log analysis would greatly benefit if all log statements could include a unique ID (AKA "fish tag") allowing correlation of logged events, whether INFOs, DEBUG/TRACE or subsequent errors.

The "start" of such an ID should be the "logical entry point" into ODL - whatever caused whatever is being logged to "happen".

Read https://logback.qos.ch/manual/mdc.html or https://logging.apache.org/log4j/2.x/manual/thread-context.html for some background; they call this a "fish tag".

Gerrit changes related to this will be on https://git.opendaylight.org/gerrit/#/q/topic:mdc