1. [RFE] OpenStack logs to include user identifier in all activity related to it 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 an user, in the logs, provides a more comprehensive view on his/her activity and helps resolve issues faster. 4. Why does the customer need this? (List the business requirements here) - To have a better understanding on the issues related to a user - To reduce the time troubleshooting issues related to an specific user - 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 a user identifier in all the logs for all the activities related to him/her * Example: Several VM requests are done by a user and some are having issues. Filtering logs by user helps getting faster to the cause 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. - Create several requests with the same user and find all the log lines with info about him/her 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.
The default configuration for most logs should already include this information. The text formatter uses the logging_user_identity_format configuration option to control which parts of the user identity are included (http://git.openstack.org/cgit/openstack/oslo.log/tree/oslo_log/_options.py#n128). Other logging handlers may place that data in separate fields or use a different format. Can you provide some more details about what we have today, and how we want that to be different? Maybe an example log line would help?
https://github.com/ViaQ/elasticsearch-templates/tree/master/namespaces and https://github.com/ViaQ/elasticsearch-templates/pull/30
*** This bug has been marked as a duplicate of bug 1454793 ***