Tracking request-id in server and within CLI

Registered by Devdatta Kulkarni on 2015-06-23

We need a way to track each request made to Solum. This is useful for several reasons, such as:
- tracking a request across different Solum services (api, worker, deployer) for purpose of debugging
- allowing users to report issue, if any, with their failed requests (https://blueprints.launchpad.net/python-glanceclient/+spec/expose-get-x-openstack-request-id)

Towards this we need to generate a unique request id for each request, and add it to the response as a header value so that it is also available in python-solumclient.

Some of the other OpenStack projects already have this feature on the server side (e.g.: Glance).
There is a discussion now happening (http://lists.openstack.org/pipermail/openstack-dev/2015-June/065599.html) to add mechanisms to obtain request ids on the client side.

Blueprint information

Status:
Not started
Approver:
Devdatta Kulkarni
Priority:
Undefined
Drafter:
Devdatta Kulkarni
Direction:
Approved
Assignee:
Vijendar Komalla
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Solum API already creates unique UUIDs for each request.

What needs to be done is the following

- add these UUIDs to our logs (Operator logs and User Logs), to allow us to search our logs and find the relevant logs for a request.
- Return the UUID with every response back to the user. I've noticed that this UUID gets sent back in come failure responses, but not all.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.