Bug 1454796

Summary:	[RFE] OpenStack logs to include project (tenant) identifier in all activity related to it
Product:	Red Hat OpenStack	Reporter:	Miguel Perez Colino <miguel>
Component:	fluentd	Assignee:	Martin Magr <mmagr>
Status:	CLOSED DUPLICATE	QA Contact:	Leonid Natapov <lnatapov>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	dhellmann, jbadiapa, mrunge, rmeggins
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-10-20 05:50:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Miguel Perez Colino 2017-05-23 13:18:21 UTC

1. [RFE] OpenStack logs to include project (tenant) 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 a project (tenant), in the logs, provides a more comprehensive view on project 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 project (tenant)
- To reduce the time troubleshooting issues related to an specific project (tenant)
- 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 project (tenant) identifier in all the logs for all the activities related to it
* Example: Several VM requests are done by a team in the same project (tenant) and they are having issues that could be related one to each other. Filtering logs by project (tenant) helps getting faster to the issues

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 request and find all the log lines with info about all the project (tenant)

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.

Comment 1 Doug Hellmann 2017-05-24 18:15:17 UTC

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?

Comment 2 Rich Megginson 2017-05-25 18:09:43 UTC

https://github.com/ViaQ/elasticsearch-templates/tree/master/namespaces
and
https://github.com/ViaQ/elasticsearch-templates/pull/30

Comment 3 Juan Badia Payno 2017-10-20 05:50:51 UTC


*** This bug has been marked as a duplicate of bug 1454793 ***