You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2020/09/25 10:16:00 UTC

[jira] [Closed] (FLINK-10244) Add option to measure latency as absolute value

     [ https://issues.apache.org/jira/browse/FLINK-10244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chesnay Schepler closed FLINK-10244.
------------------------------------
    Resolution: Won't Fix

No one is asking for this; with the performance impact of latency metrics in general it may not be required to optimize this point anyway.

> Add option to measure latency as absolute value
> -----------------------------------------------
>
>                 Key: FLINK-10244
>                 URL: https://issues.apache.org/jira/browse/FLINK-10244
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Metrics
>    Affects Versions: 1.7.0
>            Reporter: Chesnay Schepler
>            Priority: Major
>
> Latency metrics are currently organized as a histogram, which is significantly more expensive than other metric types.
> Depending on the user's metric infrastructure a histogram in Flink is overkill; several metric backends explicitly discourage measuring histograms in the application itself. Instead only the raw latency data should be exposed.
> We should add an option to expose latency not as a histogram but as a simple gauge that returns the latency based on the last received latency marker.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)