[
https://issues.apache.org/jira/browse/FLINK-17328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17195451#comment-17195451
]
Piotr Nowojski commented on FLINK-17328:
----------------------------------------
I would tend to agree with [~lining]. With monitoring the backpressure or data
skew (for which state of the buffer pools can be used), it's important to know
the topology of the job. Despite most of those informations being currently
available in one way or another via metrics, correlating information of the
subtasks/tasks buffers usage with the job graph is very painful and manual
process, while UI can present it easily in a very readable form.
> 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)
