On Fri, May 8, 2015 at 2:17 PM, Chetan Mehrotra
<[email protected]> wrote:
> On Fri, May 8, 2015 at 4:27 PM, Justin Edelson <[email protected]>
> wrote:
>> I like the idea here, but binding this to the assumption that log files are
>> stored relative to the sling home directory isn't a safe assumption. Can't
>> this be written using the Logback API and avoid reading files at all? I.e.
>> Just have log entries stored in an in-memory buffer.
>
> That would be risky as often while debugging lots of logs gets
> generated. As a user I would typically redirect all the interesting
> logs to a specific file and then have this tailer tail that. At some
> point we can provide an option to scroll also, just like in Jenkins UI
> where you can access older build logs also
But we could query the logback config and find out the defined log
files, right? The only thing that stands out for me right now is the
fact that we always look for log files under ${sling.home}/logs .
Robert
