[logback-user] Logging to a network file system

Thorbjørn Ravn Andersen thunderaxiom at hotmail.com
Mon Oct 29 16:55:57 CET 2012

If you can make the network drive appear like a local file system to your
application then you can log normally (with the added possibility that your
program will have to wait until the file system accepts the flush - this may
slow your application down).

If this is unacceptable then consider forwarding your log events to a
dedicated logging server with buffering capabilities so your application
will run at full speed.  I believe this is the business case for
Logback-audit (http://audit.qos.ch/) which is commercial software.


-----Original Message-----
From: logback-user-bounces at qos.ch [mailto:logback-user-bounces at qos.ch] On
Behalf Of Scott Ruch
Sent: 25. oktober 2012 21:35
To: logback-user at qos.ch
Subject: [logback-user] Logging to a network file system

Apologies if this has already been discussed.  I tried searching the list
archive but I didn't find anything similar.

I've been required to start logging to a network file system and I wanted to
find out what the best practices were for logback in this scenario. (IMO,
"best practice"
would be to not log to a network file system but that's not my decision.)

I've read through the documentation on the AsyncAppender and that is the
direction I am evaluating.  Any other suggestions would be appreciated.


Logback-user mailing list
Logback-user at qos.ch

More information about the Logback-user mailing list