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

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_r102726588
  
    --- Diff: 
flink-runtime-web/web-dashboard/app/scripts/modules/jobs/jobs.ctrl.coffee ---
    @@ -81,6 +78,51 @@ angular.module('flinkApp')
         JobsService.stopJob($stateParams.jobid).then (data) ->
           {}
     
    +  loadJob = ()->
    +    JobsService.loadJob($stateParams.jobid).then (data) ->
    +      $scope.job = data
    +      $scope.vertices = data.vertices
    +      $scope.plan = data.plan
    +      MetricsService.setupMetrics($stateParams.jobid, data.vertices)
    +
    +  getWatermarks = (nodes)->
    +    deferred = $q.defer()
    +    watermarks = {}
    +    jid = $scope.job.jid
    +    angular.forEach nodes, (node, index) =>
    +      metricIds = []
    +      for num in [0..node.parallelism - 1]
    +        metricIds.push(num + ".currentLowWatermark")
    +      MetricsService.getMetrics(jid, node.id, metricIds).then (data) ->
    +        values = []
    +        for key, value of data.values
    +          values.push(id: key.replace('.currentLowWatermark', ''), value: 
value)
    +        watermarks[node.id] = values
    +        if index >= $scope.plan.nodes.length - 1
    --- End diff --
    
    I have not fixed this, will try to see if I can find a more elegant 
solution.


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

Reply via email to