Proposed title of this feature request 1. [RFE] OpenStack logs to include "request id" in all objects related to the request 2. Who is behind the request? Integrated Solutions Business Unit Strategic Design Team 3. What is the nature and description of the request? To perform Openstack Operations, due to the distributed nature of the services that compose the OpenStack deployments, aggregated logging can provide a way to reduce time to perform troubleshooting, find root cause of issues, and have better insight on the health status of the Platform. Being able to correlate all the activity of all the objects related to a request, in the log provides a more comprehensive view on user activity and helps resolve issues faster. 4. Why does the customer need this? (List the business requirements here) - To have a better understanding on health status of the platform, filtered by Request - To reduce the time troubleshooting issues - To find and apply workarounds faster to the issues that may arise. 5. How would the customer like to achieve this? (List the functional requirements here) - Including "Request id" in all the logs for all the objects related to the request. * Example: A VM request is done by a user: The glance image request shall include request id, the vPort provided by nova shall include request id, the disk allocation in cinder for it shall include request id (I know most of the cases are already solved but we need to ensure that they all are covered ...) 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. - Create a request and find in all the logs the lines with info about all the objects instantiated or used during to fulfill that request. 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? No 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? No 9. Is the sales team involved in this request and do they have any additional input? No 10. List any affected packages or components. Nova Keystone Glance Cinder Neutron Fluentd ... 11. Would the customer be able to assist in testing this functionality if implemented? Yes.
This seems to correspond to this work upstream: http://specs.openstack.org/openstack/oslo-specs/specs/pike/global-req-id.html
https://github.com/ViaQ/elasticsearch-templates/tree/master/namespaces and https://github.com/ViaQ/elasticsearch-templates/pull/30
*** Bug 1454796 has been marked as a duplicate of this bug. ***
*** Bug 1454800 has been marked as a duplicate of this bug. ***
*** Bug 1418226 has been marked as a duplicate of this bug. ***
OpenStack services should include request id in messages. It is not fluentd job to track that.