Re: Sling Web Console - Log Tail Plugin

[Varun Nagpal <va...@gmail.com>]

Hi,

Apologies for a (very) late response.

As suggested by Justin and Robert, I have removed the dependency on
${sling.home}/logs/
and instead am using the Appender info in Logback Context to get the list
of log files.

Please have a look @  https://github.com/vnagpal81/sling-logtail

Thanks.
--
Varun

On Fri, May 8, 2015 at 4:53 PM, Robert Munteanu <ro...@apache.org> wrote:

> On Fri, May 8, 2015 at 2:17 PM, Chetan Mehrotra
> <ch...@gmail.com> wrote:
> > On Fri, May 8, 2015 at 4:27 PM, Justin Edelson <ju...@justinedelson.com>
> 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
>

Re: Sling Web Console - Log Tail Plugin

[Chetan Mehrotra <ch...@gmail.com>]

Hi Varun,

I tried the plugin today and it worked fine. Though the UI display is
bit awkward i.e. sliding drawer is coming at top of page for me rather
than below the WebConsole toolbar. But its pretty much functional.
Would give it try in some debugging session when working with remote
setup!. So we can probably move it to contrib first and start
improving it there

So as a first step you can open a bug and attach your source there.
For an example for the process have a look at SLING-4842

Chetan Mehrotra


On Thu, Jul 16, 2015 at 2:27 PM, Varun Nagpal <va...@gmail.com> wrote:
> Hi,
>
> Apologies for a (very) late response.
>
> As suggested by Justin and Robert, I have removed the dependency on
> ${sling.home}/logs/
> and instead am using the Appender info in Logback Context to get the list
> of log files.
>
> Please have a look @  https://github.com/vnagpal81/sling-logtail
>
> Thanks.
> --
> Varun
>
> On Fri, May 8, 2015 at 4:53 PM, Robert Munteanu <ro...@apache.org> wrote:
>
>> On Fri, May 8, 2015 at 2:17 PM, Chetan Mehrotra
>> <ch...@gmail.com> wrote:
>> > On Fri, May 8, 2015 at 4:27 PM, Justin Edelson <ju...@justinedelson.com>
>> 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
>>