Hi, Mason. Thanks for driving this Flip. I think it's important for external system to be able to perceive the metric of the operator coordinator. +1 for it.
I just have the following minor questions and am looking forward to your reply. Please forgive me if I have some misunderstandings. 1. IIRC, in a sense, operator ID and vertex ID are the same thing. The operator ID can be converted from the vertex ID[1]. Therefore, it is somewhat strange to have both vertex ID and operator ID in a single URL. 2. If I misunderstood the semantics of operator IDs here, then what is the relationship between vertex ID and operator ID, and do we need a url like `/jobs/<jobid>/vertices/<vertexid>/operators/` to list all operator ids under this vertices？ [1] https://github.com/apache/flink/blob/7bebd2d9fac517c28afc24c0c034d77cfe2b43a6/flink-runtime/src/main/java/org/apache/flink/runtime/jobgraph/OperatorID.java#L40C27-L40C27 -- Best！ Xuyang At 2024-01-12 04:20:03, "Mason Chen" <mas.chen6...@gmail.com> wrote: >Hi Devs, > >I'm opening this thread to discuss a short FLIP for exposing >JobManagerOperatorMetrics via REST API [1]. > >The current set of REST APIs make it impossible to query coordinator >metrics. This FLIP proposes a new REST API to query the >JobManagerOperatorMetrics. > >[1] >https://cwiki.apache.org/confluence/display/FLINK/FLIP-417%3A+Expose+JobManagerOperatorMetrics+via+REST+API > >Best, >Mason
