An Operator like below will expose lag between current time and event time
passing the operator. I add that after the source and before the sink, and
calculate sink_delay - source_delay in grafana. would that be a generic
solution to solve the problem?
```
public class EmitLagOperator extends Abstr
Hi,
I think we may add latency metric for each operator, which can reflect
consumption ability of each operator.
Best,
Dan Zou
> 在 2020年3月30日，18:19，Guanghui Zhang 写道：
>
> Hi.
> At flink source connector, you can send $source_current_time - $event_time
> metric.
> In the meantime, at flink si
Hi.
At flink source connector, you can send $source_current_time - $event_time
metric.
In the meantime, at flink sink connector, you can send $sink_current_time -
$event_time metric.
Then you use $sink_current_time - $event_time - ($source_current_time -
$event_time) = $sink_current_time - $source
On Mon, 30 Mar 2020 at 05:08, Lu Niu wrote:
> $current_processing - $event_time works for event time. How about
> processing time? Is there a good way to measure the latency?
>
To measure latency you'll need some way to determine the time spent between
the start and end of your pipeline.
To mea
Thanks for reply, @Zhijiang, @Congxian!
@Congxian
$current_processing - $event_time works for event time. How about
processing time? Is there a good way to measure the latency?
Best
Lu
On Sun, Mar 29, 2020 at 6:21 AM Zhijiang wrote:
> Hi Lu,
>
> Besides Congxian's replies, you can also get som
Hi Lu,
Besides Congxian's replies, you can also get some further explanations from
"https://flink.apache.org/2019/07/23/flink-network-stack-2.html#latency-tracking";.
Best,
Zhijiang
--
From:Congxian Qiu
Send Time:2020 Mar. 28 (Sa
Hi
As far as I know, the latency-tracking feature is for debugging usages, you
can use it to debug, and disable it when running the job on production.
>From my side, use $current_processing - $event_time is something ok, but
keep the things in mind: the event time may not be the time ingested in
Fl
