Bug 1041190

Summary:	[RFE][nova]: Add message ids for Warning, Error and Critical log messages
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/nova/+spec/formal-message-ids
Whiteboard:	upstream_milestone_none upstream_status_unknown upstream_definition_obsolete
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:37:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 13:53:21 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/formal-message-ids.

Description:

Having formal Message IDs assigned to Warning, Error and Critical log messages can increase the serviceability and useability of the platform. The primary purpose will be to assist with the look up of more information from a product’s documentation especially when the messages are translated. Secondary purposes would be to help stream line translations, log analysis, context correlation and improve the message feedback loop.  Informational log messages are considered self explanatory and don't require message id for additional look ups.   A batch job could be run to collect and summarize the existing messages as a starting point for a wiki page with more explanations and possible resolutions.

Specification URL (additional information):

None