[
https://issues.apache.org/jira/browse/FLINK-12680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855536#comment-16855536
]
Till Rohrmann commented on FLINK-12680:
---------------------------------------
I'm not a metrics expert but couldn't the metric system (Prometheus, Graphite,
...) do the job of the timer when using a counter? If the metric system
periodically queries a counter it could record the value with the corresponding
timestamp.
Looking at Prometheus a bit more in detail also shows that it does not support
a Timer metric type: https://prometheus.io/docs/concepts/metric_types/,
https://povilasv.me/prometheus-tracking-request-duration/
> Add timer type to metric system
> -------------------------------
>
> Key: FLINK-12680
> URL: https://issues.apache.org/jira/browse/FLINK-12680
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
> Reporter: Piyush Goyal
> Priority: Major
>
> Currently Flink metric system supports counter, gauge, histogram and meter.
> For cases which involve measuring the latency of short-term events (such as
> request latency in the context of a connector), none of these metric types is
> a good fit. Most metric system supports a timer type which is highly useful
> in such cases. Timers are useful for measuring short-duration latencies and
> the frequency of such events. All implementations of {{Timer}} report at
> least the total time and count of events as separate time series.
> Timer type will be a nice addition to the existing metric types in Flink. We
> are happy to contribute it if there is agreement on it being a good addition.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
