You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/01/31 09:03:33 UTC
[GitHub] dawidwys commented on a change in pull request #7608: FLINK-11473
[documentation][ Clarify documenation on Latency Tracking
dawidwys commented on a change in pull request #7608: FLINK-11473 [documentation][ Clarify documenation on Latency Tracking
URL: https://github.com/apache/flink/pull/7608#discussion_r252581663
##########
File path: docs/monitoring/metrics.md
##########
@@ -1628,16 +1628,18 @@ bypassing them. In particular the markers are not accounting for the time record
Only if operators are not able to accept new records, thus they are queuing up, the latency measured using
the markers will reflect that.
-All intermediate operators keep a list of the last `n` latencies from each source to compute
-a latency distribution.
-The sink operators keep a list from each source, and each parallel source instance to allow detecting
-latency issues caused by individual machines.
+The `LatencyMarker`s are used to derive a distribution of the latency between the sources of the topology and each
+downstream operator. These distributions are reported as histogram metrics. The granularity of of these distributions can
Review comment:
```suggestion
downstream operator. These distributions are reported as histogram metrics. The granularity of these distributions can
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services