Bug 994744

Summary:	Improve LogManager formatter capability: System properties, thread ID and minified category
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Kyle Lape <klape>
Component:	Logging	Assignee:	James Perkins <jperkins>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nikoleta Hlavickova <nziakova>
Severity:	unspecified	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.1.0	CC:	myarboro, olukas
Target Milestone:	ER1
Target Release:	EAP 6.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-16 18:08:13 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	994700
Bug Blocks:

Description Kyle Lape 2013-08-07 23:42:35 UTC

This would include three things:

- Hostname: We haven't find a way to get the hostname displayed in the logs. A
  simple solution would be to include System properties and therefore the
  jboss.host.name property in the pattern.

- Thread ID: Thread names are too long and of different length that disturb the
  reading of logs

- Minified log categories: Logback has a feature that lets you minify the log
  category: instead of org.jboss.logmanager.config.ConfigAction you'll get
  o.j.l.c.ConfigAction which is more readable in the logs.

An implementation should match the formatting of the same feature in existing
logging frameworks to avoid end-user confusion.

Comment 1 JBoss JIRA Server 2013-09-04 03:38:04 UTC

James Perkins <jperkins> made a comment on jira LOGMGR-67

Pull request merged

Comment 6 Ondrej Lukas 2013-10-07 10:55:11 UTC

Unfortunatelly verification failed. Thread ID and Minified log categories are ok, but setting system property works bad. If I add %${test.property} to formatter and start server with -Dtest.property=property that use "p" from word property as %p and then log of that part looks like INFOroperty.

Comment 7 James Perkins 2013-10-07 16:59:18 UTC

Looks like the expression is attempting to be resolved by server instead of allowing the logmanager to resovle the expression.

Comment 10 James Perkins 2014-09-16 18:08:13 UTC

Closing this as it mostly works in the current release. The one caveat is the system properties do not work properly. The support has been added to the log manager, but the way that expressions are parsed for attributes the system property is resolved before the value is passed to the log manager. See https://issues.jboss.org/browse/WFCORE-110 for more details.