[logback-user] Handling log events happening before configuration is ready?

[ceki]

How much time are we talking about between logback initialization and 
the time where the value of the property is known?

On 04.09.2012 14:38, Thorbjørn Ravn Andersen wrote:
> We have  done plain old “just log to a new file for the duration of the
> program – delete old logs daily” for several years now and found it
> works well for us.
>
> Now I have a rather tricky situation where part of the file name to be
> used by (a subclass of) FileAppender needs to be supplied by my code,
> but the initialization phase of the application contains log statements
> triggering the initialization of logback _/before/_ the property
> referred to by the FileAppender name string is set causing the log file
> to have an incorrect name.
>
> Basically what I have found to be the behavior I want is for logback to
> await opening the file and write data before I say it can.
>
> Question is how I can do this within the limits of logback.  Can I tell
> logback to just buffer events in memory (this will only be for a few
> seconds, and memory will most likely not be an issue) – some kind of
> valve?  Can I tell FileAppender to write to a temporary file and rename
> it whenever the name is ready (perhaps using some of the Policies from
> RollingFileAppender)?
>
> Any suggestions on how to handle this?
>
> Note:  As we restart our application daily we do not need
> RollingFileAppender for our general logging – instead we have subclassed
> FileAppender to remove “older than X days” files from the target
> folder.  This has proven to work very well for our scenario.
>
> Thanks
>
> /Thorbjørn
>
>


-- 
Ceki
http://tinyurl.com/proLogback