[
https://issues.apache.org/jira/browse/FLINK-10244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann updated FLINK-10244:
----------------------------------
Fix Version/s: 1.8.0
> 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: Metrics
> Affects Versions: 1.7.0
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Major
> Fix For: 1.7.0, 1.8.0
>
>
> 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
(v7.6.3#76005)
