Open Stack

Brian,

On Jun 4, 2013, at 1:39 PM, Brian Lamar <brian.lamar at rackspace.com> wrote:

> I'm going to refrain on commenting on thread local storage, but I have one question: Is this going to replace the request_id concept we've had in Nova/Glance for a while? I've been out of development for a bit but this seems like it's a similar concept. I'm all for having IDs to track across all projects.
> 
> Brian
> 
> 

No, it will not replace the Nova/Glance request_id.  It is intended instead to serve as a single identifier that carries across multiple services through the lifespan of a user request.  It is intended to be service-agnostic and will hopefully get implemented in every project.

Correlation_id and request_id could be the same identifier, but it could get hairy if they were.  Imagine a single call to service A results in two calls to service B.  I think you want each request to B to retain a separate request identifier for tracking purposes (like it is now), but then you want a second correlation_id that gives you simplified tracking across the entire surface of the call originating at A.

Thanks,
Brian