@danboykis you could write basically an identical appender with a different predicate check (checking the file's size): https://github.com/ptaoussanis/timbre/blob/master/src/taoensso/timbre/appenders/3rd_party/rolling.clj#L67
@bja thanks, i figured i'll have to write my own
basically you just change the predicate in that file
I think on a java.io.File you can call .length()
and just test that against whatever size
you probably have to name stuff a little differently
so that your log file knows which filename to write to
since that appender kinda assumes it can construct a log file name based on timestamp
well the timestamp isn't a bad idea to roll even with size
makes sense to order them pieces somehow
might as well order the log pieces by time
but what I mean is, when you roll, you need to either rename/move the old files and use a constant name or pick a new name
I usually specify this stuff via syslog
and just write to stdout and let the supervisor process for my jvm deal with sending to syslog
i am not sure if we're talking about the same thing or not
if I have foo.log
the moment foo.log
reaches 1gb I'll rename it to something like foo-yyyymmddss.log
i think that makes sense to do
ah
that's reasonable
that's what I meant by pieces
(that's the first of the two options I mentioned "rename/move the old files and use a constant name")
yeah
i think syslog is great, but the place where i work (java shop) everyone rolls with logback/log4j
so I am trying to not rock the boat too much