You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Piotr Nowojski (Jira)" <ji...@apache.org> on 2021/11/22 16:08:00 UTC

[jira] [Closed] (FLINK-20724) Create a http handler for aggregating metrics from whole job

     [ https://issues.apache.org/jira/browse/FLINK-20724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Piotr Nowojski closed FLINK-20724.
----------------------------------
    Resolution: Abandoned

> 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
>    Affects Versions: 1.13.0, 1.12.3
>            Reporter: Piotr Nowojski
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, stale-minor
>
> 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.20.1#820001)