we confirm that it has been implemented?
Regards,
Morgan.
*From:* Timo Walther
*Sent:* 13 December 2021 09:53:08
*To:* user@flink.apache.org
*Subject:* Re: Latency monitoring in Flink 1.14.0
Hi Morgan,
did you see th
*To:* user@flink.apache.org
*Subject:* Re: Latency monitoring in Flink 1.14.0
Hi Morgan,
did you see this:
https://stackguides.com/questions/68917956/read-flink-latency-tracking-metric-in-datadog
<https://stackguides.com/questions/68917956/read-flink-latency-tracking-metric-in-da
/KafkaSink these metrics are
just not being generated. Can we confirm that it has been implemented?
Regards,
Morgan.
From: Timo Walther
Sent: 13 December 2021 09:53:08
To: user@flink.apache.org
Subject: Re: Latency monitoring in Flink 1.14.0
Hi Morgan,
did you
Hi Morgan,
did you see this:
https://stackguides.com/questions/68917956/read-flink-latency-tracking-metric-in-datadog
Also `metrics.latency.granularity` must be set in the Flink
configuration. Not sure if `-D` forwards this properly.
Timo
On 10.12.21 18:31, Geldenhuys, Morgan Karl wrote
1) i have to set the time characteristic to event time
2) I use Flink SQL create table DDL: create table a (user_id string, ts
timestamp, data string) . so the timestampAssigner is automatically setup
using the `ts` field.
Still not sure how to get the source ingestion time to metrics system.
O
Hey Fanbin,
I’m not sure if TimeCharacteristic.IngestionTime works with Flink SQL, but if
you haven’t tried setting the stream time characteristic to ingestion time it’s
worth a shot. Otherwise, one possibility that comes to mind is to use a custom
TimestampAssigner to set the event time to the
Thanks for the insight. I was also interested in this topic.
One thought occurred to me is what about the queuing delay when sending to
your message bus (e.g. kafka). I am guessing the probe will be before the
message is added to the send queue?
Thanks again
Tim
On Thu, Jun 13, 2019, 6:08 AM
Hi Roey,
with Latency Tracking you will get a distribution of the time it took for
LatencyMarkers to travel from each source operator to each downstream
operator (per default one histogram per source operator in each non-source
operator, see metrics.latency.granularity).
LatencyMarkers are inject
