Thanks, that makes sense!
In addition, I've just found the reason for this in the code:
This is 1.5 (default value is 2000L):
https://github.com/apache/flink/blob/release-1.5/flink-core/src/main/java/org/apache/flink/configuration/MetricOptions.java#L109
This is 1.9 (default value is 0L)
https:/
Hi,
There is a release note for Flink 1.7 that could be relevant for you [1]
Granularity of latency metrics
The default granularity for latency metrics has been modified. To
restore the previous behavior users have to explicitly set the granularity
to subtask.
Best,
Gary
[1]
https://ci.
Thanks for the response.
In 1.5 the docs also state that it should be enabled [1], however, it always
worked without setting latencyTrackingInterval
[1]
https://ci.apache.org/projects/flink/flink-docs-release-1.5/monitoring/metrics.html#latency-tracking
--
Sent from: http://apache-flink-user-m
Hi Ori,
Make sure that latency metrics is enabled. It's disabled by default. See
also that the scope is set properly.
https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/metrics.html#latency-tracking
https://ci.apache.org/projects/flink/flink-docs-release-1.10/ops/config.html#metric
