<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"><base href="x-msg://6240/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Venkatesh,<div><br></div><div><div><blockquote type="cite"><div class="hmmessage" style="font-size: 12pt; font-family: Calibri; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div dir="ltr"><br>We are planning to make the correlation_id available for logging through thread local storage especially using the existing 'local.strong_store' reference. ( available from oslo-incubator/openstack/common/local.py).<br>ie., by setting the correlation_id as attribute to 'local.strong_store' in the correlation_id middleware.<br><br></div></div></blockquote><blockquote type="cite"><div class="hmmessage" style="font-size: 12pt; font-family: Calibri; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div dir="ltr">Wish to know if its good idea to use the thread local storage from local.py for correlation_id so that it could be used by respective services.<br><br></div></div></blockquote><div><br></div>My personal preference is to pass the correlation id around explicitly rather than using thread local storage. At least in Nova, there is a request context where there is already a well-established pattern of storing this type of information. </div><div><br></div></div><div>Thanks,</div><div>Brian</div></body></html>