You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Piyush Goyal (JIRA)" <ji...@apache.org> on 2019/06/03 03:00:00 UTC
[jira] [Commented] (FLINK-12680) Add timer type to metric system
[ https://issues.apache.org/jira/browse/FLINK-12680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854176#comment-16854176 ]
Piyush Goyal commented on FLINK-12680:
--------------------------------------
thanks [~yanghua] ! If you haven't started yet, we (at netflix) already have a timer implementation in our local flink fork that we can contribute. If you are okay with it, feel free to assign the Jira to me.
> Add timer type to metric system
> -------------------------------
>
> Key: FLINK-12680
> URL: https://issues.apache.org/jira/browse/FLINK-12680
> Project: Flink
> Issue Type: Improvement
> Reporter: Piyush Goyal
> Assignee: vinoyang
> 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)