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 2019/05/10 09:29: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=16837090#comment-16837090 ]
Chesnay Schepler commented on FLINK-12423:
------------------------------------------
you could just use a histogram and encode the unit in the metric name.
> 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)