...
- Doesn't cater to usual developer interactions with logs - tail'ing (with log file monitoring
-f
) or less'ing (viewing the log) or downloading - Hard to distinguish between two log lines
- Exception stack traces are virtually un-readable
- Virtually no formatting in the UI - almost rendered as the logs appear from the backend, which is not ideal to an end-user
- No search (even at the UI level)
- No way to download logs
- No way to distinguish whether logs are live or past
Jira Legacy server Cask Community Issue Tracker serverId 45b48dee-c8d6-34f0-9990-e6367dc2fe4b key CDAP-5733
User Stories:
- As a Hydrator/CDAP user, I want to be able to view my pipeline logs from both currently running pipelines as well as past pipelines to effectively debug the pipeline during failures
- As a Hydrator/CDAP user, I want to clearly know if the logs I am viewing are being updated live or are from a past run
- As a Hydrator/CDAP user, I want greater emphasis on the most important part of logs - the messages
- As a Hydrator user, I do not want logs to be flooded with stack traces. I want the ability to suppress them individually and as a whole
- As a Hydrator/CDAP user, I want to be able to view logs in the selected time range
- As a Hydrator/CDAP user, I want the ability to download complete log files
- As a Hydrator/CDAP user, I want to view a summary of the logs I'm viewing (the number of messages, the number of errors, the number of warnings)
- As a Hydrator/CDAP user, I want to be able to filter logs by the lowest log level
- As a Hydrator/CDAP user, I want to be able to filter logs by keywords
Possible solutions
- Tabular view: Columns for date, Class Name/Thread Name, Log Level, Log Line
- Alternate row background colors
- Vertically expandable with scrolling
- Searchable (Filter-able) columns
- Clear demarcation of rows
- Horizontally scrollable rows
- Snippet with expand - especially for stack traces
- Picking only 1 or more log level -INFO, DEBUG, WARN, ERROR, ALL
- Ability to view and download raw logs if required
- Ability to view and expand only the "content" column of a log line
- Time range picker
- Ability to show the hostname where the logfile came from (Probably only makes sense if we ever show logs for services that run on fixed hosts, not for programs that run in YARN containers).
- Ability to show the path to the log file on the host (Probably only makes sense if we ever show logs for services that run on fixed hosts, not for programs that run in YARN containers).
Use Case 2: Bottom Panel
Problems with current Bottom Panel
...