Open Stack

On 06/04/2013 02:45 PM, Sandy Walsh wrote:
> 
> 
> On 06/04/2013 02:24 PM, Venkatesh Sampath wrote:
>> Hi Everyone,
>>
>> We are planning to introduce a correlation_id across for effective
>> debugging of requests that span across services.
>>
>> The idea is to pass the correlation_id as part of the request header
>> across services. The job of generating/capturing the correlation_id and
>> setting it as part of the request header is done through the
>> correlation_id.py middleware available through oslo incubator.
> 
> Why not use the existing Request ID? It's already stored in the Context
> object.

Is there a document about this feature, including how it relates to the
existing request ID, that we can all review?


> 
>>
>> The services that uses the correlation_id middleware can in turn obtain
>> the correlation_id from the request header and use it as part of logging
>> & notification purposes.
>>
>> 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).
>> ie., by setting the correlation_id as attribute to 'local.strong_store'
>> in the correlation_id middleware.
>>
>> 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.
>>
>> Thoughts?


-- 
Russell Bryant