unsubscribe On Thu, Jul 16, 2015 at 1:41 AM, Amareshwari Sriramadasu (JIRA) < [email protected]> wrote:
> > [ > https://issues.apache.org/jira/browse/LENS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629433#comment-14629433 > ] > > Amareshwari Sriramadasu commented on LENS-602: > ---------------------------------------------- > > I changed the current log4j to logback xml and used SiftingAppender. The > files are getting separated and we should be to serve them on rest. I'll go > ahead create subtasks here and link related jiras to move to logback. > > > Easy access to per-query lens server logs > > ----------------------------------------- > > > > Key: LENS-602 > > URL: https://issues.apache.org/jira/browse/LENS-602 > > Project: Apache Lens > > Issue Type: New Feature > > Reporter: Angad Singh > > Assignee: Amareshwari Sriramadasu > > Labels: Hackathon-July > > > > Right now one has to have access to the lens server machine and find a > lens query's job logs manually in lensserver.log file. This is neither > scalable nor user-friendly for a shared multi-tenanted lens server. > > Just throwing server-exceptions to the client or showing the job ID is > also often not enough. Even when the query succeeds, one needs to see how > candidate fact tables and their columns, etc. were pruned and how join > chains were resolved, for example. That is only possible by seeing the lens > server logs. > > Instead of that, this ticket is to propose that lens store logs for each > lens query in a different log file on the server and that there be a REST > end point to access a query's log (by query ID). That URL can be pasted on > the client shell when the query is launched and the user can see a tailed > log of all that lens is doing behind the scenes. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
