[logback-user] Overriding the logback file in an application via a system property

Michael McCarthy mikeycmccarthy at gmail.com
Thu Feb 9 19:30:52 CET 2012

I'm an application developer currently working with our sysops team around
logging. Their problem is that everyone who writes an app logs in entirely
their own way, often to the filesystem with no consideration for a
standardised logging format.

I've been looking into logback and so far so good...my idea is that when a
developer deploys to the container, the container overrides the logback.xml
file via the system property with it's own one, that then logs via gelf to
something like graylog.

I've been trying this locally and I don't seem to get any messages being
sent to graylog...my suspicion is that jboss finds the application's
logback file then ignores the system property. Am I correct in assuming
this is right, or should the system property override the logback that is
in the jar?

Out of interest, does this seem a valid solution for standardised logging?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-user/attachments/20120209/307ef3f7/attachment.html>

More information about the Logback-user mailing list