[
https://issues.apache.org/jira/browse/FLINK-14136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328278#comment-17328278
]
Flink Jira Bot commented on FLINK-14136:
----------------------------------------
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.
> Operator Topology and Metrics Inside Vertex
> -------------------------------------------
>
> Key: FLINK-14136
> URL: https://issues.apache.org/jira/browse/FLINK-14136
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Web Frontend
> Reporter: Yadong Xie
> Priority: Major
> Labels: stale-major
> Attachments: Kapture 2019-09-17 at 14.31.46.gif, screenshot.png,
> screenshot2.png
>
>
> In the screenshot below, users can get vertex topology data in the job detail
> page, but the operator topology and metrics inside vertex is missing in the
> graph.
> !screenshot.png|width=477,height=206!
> There are actually two operators in the first vertex, their names are Source:
> Custom Source and Timestamps/Watermarks, but users can only see Source:
> Custom Source -> Timestamps/Watermarks in the vertex level.
> We can already get some metrics at the operator-level such as records-in and
> records-out from the metrics REST API (in the screenshot below).
> !screenshot2.png|width=475,height=210!
> If we can get the operators’ topology data inside a vertex, users can the
> whole operator topology with record-received and records-sent information
> after a glance at the graph, we think it would be quite useful to
> troubleshoot jobs’ problem when it is running. Here is a demo in the gif
> below.
> !Kapture 2019-09-17 at 14.31.46.gif|width=563,height=286!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
