Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
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.