]
RH Bugzilla Integration commented on LOGMGR-67:
-----------------------------------------------
James Perkins <jperkins(a)redhat.com> changed the Status of [bug
Improve LogManager formatter capability: System resources, thread ID
and minified category
------------------------------------------------------------------------------------------
Key: LOGMGR-67
URL:
https://issues.jboss.org/browse/LOGMGR-67
Project: JBoss Log Manager
Issue Type: Feature Request
Components: core
Affects Versions: 1.3.2.Final
Environment: JBoss EAP 6.0.1
Reporter: Jeremy KUHN
Assignee: James Perkins
Labels: jboss
Fix For: 1.5.0.Final, 2.0.0.Beta1
Original Estimate: 4 hours
Remaining Estimate: 4 hours
Hello,
We are currently developing a major JEE application running on multiple JBoss EAP 6.0.1
instances in a service oriented architecture.
The current implementation of JBoss-logmanager (1.3.2.Final) shipped with JBoss EAP
doesn't provide the functionality we require in term of logging formatting.
We are missing:
- Thread ID (Thread names are too long and of different length that disturb the reading
of logs)
- we haven't find a way to get the hostname displayed in the logs, a simple solution
would be to be able to include System properties and therefore the jboss.host.name
property in the pattern. System properties would also be interesting to identified the log
coming from a specific application (we'll have one application deployed per JBoss
instance). Ideally, we'd like to have the ability to provide a context name to know
which application has logged the event but this seems to have been delivered with logging
profiles.
- logback has this interesting 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.
Regards