Re: Using latency markers

his problem. It is just a new feature to > provide more functionality for user to use metric system. > > Regards, > Tony Wei > > 2017-12-26 18:23 GMT+08:00 Marvin777 <xymaqingxiang...@gmail.com>: > >> Hi, >> >> I just want to say we're having the same issues.

Re: Using latency markers

. Using latency markers > <http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Using-latency-markers-td14791.html#a14799> > > I get NaN in the Task metrics. The version is 1.3.1. > > Maybe I'm completely missing something... > > And there are questions abo

Re: Using latency markers

Hi all! I'm having the same issues. I get NaN in the Task metrics. The version is 1.3.1. Maybe I'm completely missing something... There are questions about FLINK-7692, it can Solve the problem above? What should I do in my version. Thanks! 2017-10-11 23:30 GMT+08:00 Aljoscha Krettek

Re: Using latency markers

This is the Jira issue: https://issues.apache.org/jira/browse/FLINK-7608 > On 27. Sep 2017, at 12:22, Martin Eden wrote: > > Any follow-up on this? Jira? PR? > > On Wed, Sep 13, 2017 at 11:30 AM, Tzu-Li (Gordon) Tai >

Re: Using latency markers

Any follow-up on this? Jira? PR? On Wed, Sep 13, 2017 at 11:30 AM, Tzu-Li (Gordon) Tai wrote: > Hi Aitozi, > > Yes, I think we haven’t really pin-pointed out the actual cause of the > problem, but if you have a fix for that and can provide a PR we can > definitely look at

Re: Using latency markers

Hi Aitozi, Yes, I think we haven’t really pin-pointed out the actual cause of the problem, but if you have a fix for that and can provide a PR we can definitely look at it! That would be helpful. Before opening a PR, also make sure to first open a JIRA for the issue (I don’t think there is one

Re: Using latency markers

Hi, Aljoscha, the dashboard shown NAN is just because the value of the latencyGague is not numerical， so it can't be shown in dashboard, i removed the other latencydescprition except the sink, so i can see the latency in dashboard, do i need to post a pr? thanks, Aitozi -- Sent from:

Re: Using latency markers

Yes, they are enabled by default I think. Gyula On Fri, Aug 11, 2017, 14:14 Aljoscha Krettek wrote: > It seems you have to enable latency tracking > via ExecutionConfig.setLatencyTrackingInterval(...). This will make the > sources emit latency tokens, which then in turn

Re: Using latency markers

It seems you have to enable latency tracking via ExecutionConfig.setLatencyTrackingInterval(...). This will make the sources emit latency tokens, which then in turn update the latency metric: https://ci.apache.org/projects/flink/flink-docs-release-1.3/monitoring/metrics.html#latency-tracking

Re: Using latency markers

Hi, I just want to say we're having the same issues. There's no metric for latency when we attempted to export the metrics through graphite either. Regards, Kien On 8/10/2017 7:36 PM, Aljoscha Krettek wrote: Hi, I must admit that I've never used this but I'll try and look into it.

Re: Using latency markers

Hi, I must admit that I've never used this but I'll try and look into it. Best, Aljoscha > On 10. Aug 2017, at 11:10, Gyula Fóra wrote: > > Hi all! > > Does anyone have a working example of using the latency markers to test for > the topology latency? > We are using

Using latency markers

Hi all! Does anyone have a working example of using the latency markers to test for the topology latency? We are using Flink 1.3.2 and it seems like however we tune it, whatever job we use all we get is NaN in the metrics. Maybe we are completely missing something... Thanks! Gyula