Log Request ID Mappings (partial)

Registered by Chris Buccella

Each OpenStack service has sends a request ID header with HTTP responses. This value can be useful for tracking down problems in the logs. However, when operations cross service boundaries, this tracking can become difficult, as
each service has its own request ID. This becomes especially problematic when requests are coming in parallel. For example, nova will call to glance for images, but that glance instance may be handling several other requests at the same time. By logging a mapping of nova's request ID and glance's request ID on the same log line, the user can easily find the glance request ID that is related to his nova request in the n-api log. That glance request ID can then be searched for in glance's logs.

Blueprint information

John Garbutt
Needs approval
Series goal:
Milestone target:
Started by
John Garbutt

Related branches



Gerrit topic: https://review.openstack.org/#q,topic:bp/log-request-id-mappings,n,z

Addressed by: https://review.openstack.org/86403
    Log Request ID Mappings

Added to Juno series, as nova-spec is reviewed, please add some code, to prove you are going to make the milestone before this can be approved. --johnthetubaguy (8th May 2014)

I can see code up for review now, so approving the blueprint --johnthetubaguy (23rd May 2014)

Addressed by: https://review.openstack.org/69538
    Sync request_utils from oslo

Addressed by: https://review.openstack.org/68518
    Log request IDs between nova and glance

Addressed by: https://review.openstack.org/95045
    Refactor calls to cinderclient()

Juno-1 is very soon, this is at risk of being punted into Juno-2, so marking as slow progress. Please request the people with -2 to remove them when you restore the change, so we can move more quickly with the reviews. Do catch me in IRC for questions. --johnthetubaguy (30 May 2014)

Doesn't seem to be getting any closer - external dependency on glance client change, moving to juno-1 --johnthetubaguy 9th May 2014

Addressed by: https://review.openstack.org/106878
    WIP: Log request IDs between nova and cinder

No more progress, punting this to juno-3 --johnthetubaguy (15ht July 2014)

No more progress, so new patches are punted out of juno now, glance stuff can stay --johnthetubaguy 21st August 2014

Sorry, this does not have enough positive reviews to make it for juno-3, please resubmit for kilo. For more information, please contact me (johnthetubaguy) via IRC or email. --johnthetubaguy 2nd September 2014

Addressed by: https://review.openstack.org/132819
    Log Request ID Mappings

Addressed by: https://review.openstack.org/152820
    Extract cinder-client response to log request IDs

Addressed by: https://review.openstack.org/154358
    log request id mappings from cinder

Addressed by: https://review.openstack.org/173234
    log request-id mapping of nova and cinder

Please note you need to submit a nova-spec to get this blueprint approved for liberty. http://docs.openstack.org/developer/nova/blueprints.html --johnthetubaguy 22nd June 2015

Current code review is, no spec review seen anywhere.

Addressed by: https://review.openstack.org/187948
    Extract cinder-client response to log request IDs

Sorry, we are not longer accepting nova-specs or blueprints for liberty.
Please submit a backlog nova-spec, so it is ready for the next release.
For more details, please see: https://wiki.openstack.org/wiki/Nova/Liberty_Release_Schedule
--johnthetubaguy 15th July 2015


Work Items

Work items:
1) Sync request_utils module from oslo: INPROGRESS
2) Using request_utils, log nova<->glance interactions: INPROGRESS
3) Using request_utils, log nova<->cinder interactions: POSTPONED
4) Using request_utils, log nova<->neutron interactions: POSTPONED