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/10 18:11:00 UTC
[jira] [Commented] (FLINK-12423) Add Timer metric type for
flink-metrics module
[ https://issues.apache.org/jira/browse/FLINK-12423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16860215#comment-16860215 ]
Piyush Goyal commented on FLINK-12423:
--------------------------------------
At Netflix, we use Atlas([https://github.com/Netflix/atlas/wiki)] as our metric system. We found it difficult to incorporate latency related metrics in Elasticsearch connector due to lack of a timer metric type in Flink. I think it will be useful to have it. I had opened FLINK-12680 which was a dupe of this issue.
> Add Timer metric type for flink-metrics module
> ----------------------------------------------
>
> Key: FLINK-12423
> URL: https://issues.apache.org/jira/browse/FLINK-12423
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
> Reporter: Armstrong Nova
> Assignee: Armstrong Nova
> Priority: Major
>
> Hi guys,
> Currently, Flink only support 4 registering metrics, {{Counters}}, {{Gauges}}, {{Histograms}} and {{Meters}}. If we want to measure the time cost metric, for example P75th, P99th, P999th， right now can only use Histograms metric. But Histograms metric not support TimeUnit type (second, millisecond, microsecond, nanosecond). So it's not convenient to collaborate with outside metric system.
> The Codahale/DropWizard support Time meter, so we can wrap it in Flink.
> Flink metrics doc [https://ci.apache.org/projects/flink/flink-docs-master/monitoring/metrics.html]
> Thanks for your time.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)