Bug 1042239 - [RFE][heat]: Log request ID
Summary: [RFE][heat]: Log request ID
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/heat...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 21:29 UTC by RHOS Integration
Modified: 2015-03-28 04:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:06:50 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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
Note You need to log in before you can comment on or make changes to this bug.