Bug 1042239

Summary: [RFE][heat]: Log request ID
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/heat/+spec/log-request-id
Whiteboard: upstream_milestone_none upstream_status_implemented upstream_definition_review
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:06:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 21:29:15 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/heat/+spec/log-request-id.

Description:

Each request to the API should have a unique request ID.  For example:

req-15187ebf-19bc-4210-b733-56b04d5dabd2

This is built into oslo. The request ID should be in each log message generated by heat-engine and heat-api.
In a production Heat deployment, this would facilitate tracing the conversation through all the tiers and aid in debugging.

Specification URL (additional information):

None