[
https://issues.apache.org/jira/browse/LENS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626173#comment-14626173
]
Srikanth Sundarrajan commented on LENS-602:
-------------------------------------------
I would suggest we consider an alternate appender to collect log lines for a
query (with additivity=true), which can then be used as is for query log as
opposed to grepping a general lens server log file for a query id. This will
essentially conflict with log compression & rotation policy otherwise.
> 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)
