add regex filter option when tailing remote logs

[sodul]

Something equivalent to tail -500 out.log | grep foo. The current implementation only does tail -500 out.log. Highlighting the matching patterns would a be a bonus.

[ypujante]

You can already do this with the commands feature. Isn't it working? Or did you have something else in mind?

[sodul]

1. The commands feature is not available to read-only users. So this feature would improve the ability to troubleshoot production system while keeping limited access.
2. With the live tail option this becomes quite powerful.

Sent from my iPhone

On Sep 2, 2013, at 4:21 PM, Yan Pujante notifications@github.com wrote:

You can already do this with the commands feature. Isn't it working? Or did you have something else in mind?

— Reply to this email directly or view it on GitHub.

[ypujante]

How do you picture the "grep foo" part working in the UI? Do you essentially do a tail which goes to a page in which there is a textfield to put the rest of the pipe? I am kind of struggling to imagine how it looks/works.

I could totally imagine extending glu so that the list of commands under each mountPoint can be configurable, but I am sure that the "grep foo" piece can be anything (at runtime).

Since you have already done it somewhere else, can you share the UI design for it?

[sodul]

Here is a mockup of how it could look like.

I would not add highlighting in the first iteration but would be good further down the road. Jenkins logs are very nice as they add timestamps and make urls clickable. The 'raw log' link would point to the current implementation, or even allow to download the actual file (without a tail, so things like zip files would be downloadable).

[ypujante]

That is pretty cool. I will start thinking about it :)

[ypujante]

5.3.0 brings the basis for this kind of future enhancements :)