Hi, So far I don't have any updates but I still want to look at this.
Best, Aljoscha > On 13. Sep 2017, at 11:46, Tzu-Li (Gordon) Tai <tzuli...@apache.org> wrote: > > Hi, > > There is actually latency metrics in the Web UI, but I think there was also > some previously reported problem on that [1]. > Is there a JIRA for the patch work you did that you mentioned? If you have a > fix for that we could definitely have a look at it. > > Looping in Aljoscha also, who I think was looking into the issue of latency > metrics not showing and may have some status updates on that. > > Cheers, > Gordon > > [1] > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Using-latency-markers-td14791.html#a14799 > > <http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Using-latency-markers-td14791.html#a14799> > > On 10 September 2017 at 8:39:46 AM, aitozi (gjying1...@gmail.com > <mailto:gjying1...@gmail.com>) wrote: > >> Hi, >> >> You are right, i have proved that the backpressure will increase the >> latency,and in have another question, now the value of the latency is not >> Visualization in the dashboard,is there any plan to do this, i have add this >> by remove the other operator and only keep the source -> end latency and >> then i can see the latency in dashboard, if the community accept the patch >> >> Thanks. >> >> and now the >> Tzu-Li (Gordon) Tai wrote >> > Hi! >> > >> > Yes, backpressure should also increase the latency value calculated from >> > LatencyMarkers. >> > LatencyMarkers are special events that flow along with the actual stream >> > records, so they should also be affected by backpressure. >> > >> > Are you asking because you observed otherwise? >> > >> > Cheers, >> > Gordon >> > >> > >> > >> > -- >> > Sent from: >> > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/ >> >> >> >> >> >> -- >> Sent from: >> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/