[
https://issues.apache.org/jira/browse/FLINK-12953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873759#comment-16873759
]
vinoyang commented on FLINK-12953:
----------------------------------
Hi [~rmetzger] Agree. In our streaming platform, we have strong requirements
about listing old log files for viewing. You know, for long-running streaming
applications, we usually configure rolling file strategy based on log
frameworks(log4j or logback) otherwise, the size of a single log file would be
very large. Currently, Flink only allows users to view the latest log files,
it's not easy for users to location some problems which have a relationship
with old-time.
> 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)
