[
https://issues.apache.org/jira/browse/FLINK-20724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327449#comment-17327449
]
Flink Jira Bot commented on FLINK-20724:
----------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Create a http handler for aggregating metrics from whole job
> ------------------------------------------------------------
>
> Key: FLINK-20724
> URL: https://issues.apache.org/jira/browse/FLINK-20724
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
> Reporter: Piotr Nowojski
> Priority: Major
> Labels: stale-major
> Fix For: 1.13.0
>
>
> This is an optimisation idea.
> Create a similar http handler to {{AggregatingSubtasksMetricsHandler}}, but
> one that would aggregate metrics per task, from all of the job vertices. The
> new handler would only take {{JobID}} as a parameter. So that Web UI can in
> one RPC obtain {{max(isBackPressureRatio)}} /
> {{max(isCausingBackPressureRatio)}} per each task in the job graph.
> This is related to FLINK-14712, where we are invoking more REST calls to get
> the statistics per each task/node (in order to color the nodes based on the
> back pressure and busy times). With this new handler, WebUI could make a one
> REST call to get all the metrics it needs, instead of doing one REST call per
> every Task.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
