[ 
https://issues.apache.org/jira/browse/FLINK-12953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873145#comment-16873145
 ] 

vinoyang commented on FLINK-12953:
----------------------------------

Hi [~rmetzger] thanks for being interested in this issue.

Actually, we have split business log of usersĀ from the TaskManager log in our 
inner flink fork. More details please see FLINK-11202. I wrote a design 
document (see the description of FLINK-11202) and started a discussion in Flink 
dev mailing thread. Unfortunately, few peoples are interested in this issue.

About your thought that providing a special logger instance, I am afraid it 
does not work. Currently, Flink uses log4j1.x and all log related classes are 
delegated to the classloader of the Flink framework. What's more, Flink 
actively specify the log file and log configuration with {{-Dlog.xxx}} which 
prevents scalability.

In addition, I created a ticket about enhancing TaskManager log visualization 
by listing all log files for Flink web UI(FLINK-11782). I think it's a good 
improvement for Flink web UI.

> 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)

Reply via email to