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.
James Perkins <jperkins> made a comment on jira LOGMGR-67 Pull request merged
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.
Looks like the expression is attempting to be resolved by server instead of allowing the logmanager to resovle the expression.
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.