[
https://issues.apache.org/jira/browse/FLINK-12953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16872011#comment-16872011
]
Chad Dombrova commented on FLINK-12953:
---------------------------------------
The Task Manager has the same kind of sprawling log as the Job Manager, so the
user story presented here is still valid: just replace the words "Job Manager"
with "Task Manager".
The current UX is this:
- submit a job
- go to the Task Manager view and choose log
- scroll to the bottom
- search for messages pertaining to your job amidst all the other logging from
other jobs and general flink output
- refresh and repeat
I highly recommend that you try out Dataflow so that you can understand the
desired UX. It lets you narrow down to just the logs of the current job or
transform.
> View logs from Job view in Web Dashboard
> ----------------------------------------
>
> Key: FLINK-12953
> URL: https://issues.apache.org/jira/browse/FLINK-12953
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Web Frontend
> Reporter: Chad Dombrova
> Priority: Major
>
> As a (beam) developer I want to be able to print/log information from my
> custom transforms, and then monitor that output within the job view of the
> Web Dashboard, so that I don't have to go hunting through the combined log in
> the Job Manager view. The Job Manager log has way too much in it, spanning
> all jobs, including output logged by both flink and user code.
> A good example of how this UX should work can be found in Google Dataflow:
> - click on a job, and see the logged output for that job
> - click on a transform, and see the logged output for just that transform
> thanks!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
