[
https://issues.apache.org/jira/browse/FLINK-17328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17195454#comment-17195454
]
Chesnay Schepler commented on FLINK-17328:
------------------------------------------
If the matching of such metrics to the JobGraph is painful, then I don't see
how exposing these in the UI solves anything. I would think that a better goal
would be to have the REST API provide a more high-level take on where
back-pressure is, instead of exposing a bunch of low-level metrics and doing
matching in the UI.
> Expose network metric for job vertex in rest api
> ------------------------------------------------
>
> Key: FLINK-17328
> URL: https://issues.apache.org/jira/browse/FLINK-17328
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Metrics, Runtime / REST
> Reporter: lining
> Assignee: lining
> Priority: Major
> Labels: pull-request-available
>
> JobDetailsHandler
> * pool usage: outPoolUsageAvg, inputExclusiveBuffersUsageAvg,
> inputFloatingBuffersUsageAvg
> * back-pressured for show whether it is back pressured(merge all iths
> subtasks)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
