[
https://issues.apache.org/jira/browse/FLINK-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880563#comment-15880563
]
ASF GitHub Bot commented on FLINK-3427:
---------------------------------------
Github user nellboy commented on a diff in the pull request:
https://github.com/apache/flink/pull/3366#discussion_r102726782
--- Diff:
flink-runtime-web/web-dashboard/app/scripts/modules/jobs/jobs.ctrl.coffee ---
@@ -318,3 +360,7 @@ angular.module('flinkApp')
loadMetrics() if $scope.nodeid
# --------------------------------------
+
+.controller 'JobPlanWatermarksController', ($scope) ->
--- End diff --
This controller is no longer empty, but we still needed to register it as a
controller, so yes, we needed it.
> Add watermark monitoring to JobManager web frontend
> ---------------------------------------------------
>
> Key: FLINK-3427
> URL: https://issues.apache.org/jira/browse/FLINK-3427
> Project: Flink
> Issue Type: Improvement
> Components: Streaming, Webfrontend
> Reporter: Robert Metzger
>
> Currently, its quite hard to figure out issues with the watermarks.
> I think we can improve the situation by reporting the following information
> through the metrics system:
> - Report the current low watermark for each operator (this way, you can see
> if one operator is preventing the watermarks to rise)
> - Report the number of events arrived after the low watermark (users can see
> how accurate the watermarks are)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
