https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/INFRAUTILS-15 infrautils <p>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.</p> <p>The "start" of such an ID should be the "logical entry point" into ODL - whatever caused whatever is being logged to "happen".</p> <p>Read <a href="https://logback.qos.ch/manual/mdc.html" class="external-link" target="_blank" rel="nofollow noopener">https://logback.qos.ch/manual/mdc.html</a> or <a href="https://logging.apache.org/log4j/2.x/manual/thread-context.html" class="external-link" target="_blank" rel="nofollow noopener">https://logging.apache.org/log4j/2.x/manual/thread-context.html</a> for some background; they call this a "fish tag".</p> <p>Gerrit changes related to this will be on <a href="https://git.opendaylight.org/gerrit/#/q/topic:mdc" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/q/topic:mdc</a></p> <p>Operating System: All<br/> Platform: All</p> INFRAUTILS-15

All log statements should include a unique ID (AKA "fish tag") allowing correlation

Improvement Low Confirmed Unresolved Unassigned Michael Vorburger Fri, 28 Jul 2017 09:30:44 +0000 Tue, 29 Sep 2020 20:43:13 +0000 Nitrogen General 0 1 <p>This is a cross-cutting concern and requires a wee bit more design thinking before we jump into implementation.</p> <p>Specifically we need to understand (at the architecture level) which points in the system assign these tags. Are these requests from RESTCONF? Are these internal events? How granular are there? How do they map at multiple levels – i.e. what happens if a single request ends up creating multiple datastore transactions? Are the tags unique within a cluster? Which channels are required to propagate them?</p> Development External issue ID 8904 External issue URL Issue Type ODL SR Target Milestone Rank 0|i01miv: