Hi Puneet, > Read about latency markers but not much useful as it just skips time taken > by each operator.
Yes, latency-tracking indeed has the problem you said. Is there any way to track latency / time taken for each event processing. I'm afraid there is no built-in way to track latency / time taken for each event processing. If the job is a simple ETL job, you may could track each element latency by: 1. calculate a start_time in source 2. calculate end_time in the sink 3. calculate the latency by end_time - start_time. But if the job has aggregate operator, it's hard to track latency for each event processing because a group of raw records would be aggregated into an accumulator result. Best, JING ZHANG Puneet Duggal <puneetduggal1...@gmail.com> 于2021年10月21日周四 上午1:21写道： > Hi, > > Is there any way to track latency / time taken for each event processing. > Read about latency markers but not much useful as it just skips time taken > by each operator. > > Thanks, > Puneet
