Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 5C1C020049C for ; Fri, 11 Aug 2017 15:44:36 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5A96B16D452; Fri, 11 Aug 2017 13:44:36 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 7933E16D44D for ; Fri, 11 Aug 2017 15:44:35 +0200 (CEST) Received: (qmail 35695 invoked by uid 500); 11 Aug 2017 13:44:34 -0000 Mailing-List: contact user-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list user@flink.apache.org Received: (qmail 35684 invoked by uid 99); 11 Aug 2017 13:44:34 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Aug 2017 13:44:34 +0000 Received: from aljoschas-mbp.fritz.box (ipservice-092-219-057-167.092.219.pools.vodafone-ip.de [92.219.57.167]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id CFA641A0019; Fri, 11 Aug 2017 13:44:32 +0000 (UTC) From: Aljoscha Krettek Message-Id: <66DA2E1C-C353-4021-B9BB-7635C6EC7046@apache.org> Content-Type: multipart/alternative; boundary="Apple-Mail=_04BDFE48-27D3-4E81-B281-50D9D1FB9699" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Using latency markers Date: Fri, 11 Aug 2017 15:44:29 +0200 In-Reply-To: <6ae89c96-a1a2-b84b-ea50-62280fd309fe@gmail.com> Cc: =?utf-8?Q?Gyula_F=C3=B3ra?= , user@flink.apache.org To: Kien Truong References: <07EB8D32-ED51-4768-A350-3754EC4DADBD@apache.org> <560BFB25-5AE7-4485-BD18-71F4ACC1ED5E@apache.org> <6ae89c96-a1a2-b84b-ea50-62280fd309fe@gmail.com> X-Mailer: Apple Mail (2.3273) archived-at: Fri, 11 Aug 2017 13:44:36 -0000 --Apple-Mail=_04BDFE48-27D3-4E81-B281-50D9D1FB9699 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Ok, I can also confirm that it doesn't work. I'll look into this and = will let you know what I find. Best, Aljoscha > On 11. Aug 2017, at 14:57, Kien Truong = wrote: >=20 > Yes, we also tried changing the tracking interval to no avail, still = no latency metric. > Kien >=20 > On 8/11/2017 7:26 PM, Gyula F=C3=B3ra wrote: >> Yes, they are enabled by default I think. >>=20 >> Gyula >>=20 >>=20 >> 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 update the latency = metric: = https://ci.apache.org/projects/flink/flink-docs-release-1.3/monitoring/met= rics.html#latency-tracking = . >>=20 >> Did you enable that? >>=20 >> Best, >> Aljoscha >>=20 >>=20 >>> On 10. Aug 2017, at 18:36, Kien Truong > wrote: >>>=20 >>> Hi, >>>=20 >>> I just want to say we're having the same issues. >>>=20 >>> There's no metric for latency when we attempted to export the = metrics through graphite either. >>>=20 >>>=20 >>> Regards, >>>=20 >>> Kien >>>=20 >>>=20 >>> On 8/10/2017 7:36 PM, Aljoscha Krettek wrote: >>>> Hi, >>>>=20 >>>> I must admit that I've never used this but I'll try and look into = it. >>>>=20 >>>> Best, >>>> Aljoscha >>>>=20 >>>>> On 10. Aug 2017, at 11:10, Gyula F=C3=B3ra > wrote: >>>>>=20 >>>>> Hi all! >>>>>=20 >>>>> 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... >>>>>=20 >>>>> Thanks! >>>>> Gyula >>>=20 >>=20 >=20 --Apple-Mail=_04BDFE48-27D3-4E81-B281-50D9D1FB9699 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Ok, I can also confirm that it doesn't work. I'll look into = this and will let you know what I find.

Best,
Aljoscha

On 11. Aug 2017, at 14:57, Kien = Truong <duckientruong@gmail.com> wrote:

=20 =20

Yes, = we also tried changing the tracking interval to no avail, still no latency metric.

Kien

On 8/11/2017 7:26 PM, Gyula F=C3=B3ra = wrote:

Yes, they are enabled by = default I think.

Gyula


On Fri, Aug 11, 2017, 14:14 Aljoscha = Krettek <aljoscha@apache.org> wrote:
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/mon= itoring/metrics.html#latency-tracking.

Did you enable that?

Best,
Aljoscha


On 10. Aug 2017, at 18:36, Kien Truong = <duckientruong@gmail.com> wrote:

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.

Best,
Aljoscha

On 10. Aug = 2017, at 11:10, Gyula F=C3=B3ra <gyula.fora@gmail.com> wrote:

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




= --Apple-Mail=_04BDFE48-27D3-4E81-B281-50D9D1FB9699--