You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Arpit Agarwal (Jira)" <ji...@apache.org> on 2019/11/22 17:47:00 UTC
[jira] [Resolved] (HDDS-2300) Publish normalized Ratis metrics via
the prometheus endpoint
[ https://issues.apache.org/jira/browse/HDDS-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Agarwal resolved HDDS-2300.
---------------------------------
Fix Version/s: 0.5.0
Target Version/s: (was: 0.5.0)
Resolution: Fixed
+1 I've committed this. Thanks for the contribution [~elek] and [~adoroszlai].
> Publish normalized Ratis metrics via the prometheus endpoint
> ------------------------------------------------------------
>
> Key: HDDS-2300
> URL: https://issues.apache.org/jira/browse/HDDS-2300
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Marton Elek
> Assignee: Marton Elek
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.5.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Latest Ratis contains very good metrics about the status of the ratis ring.
> After RATIS-702 it will be possible to adjust the repoter of the Dropwizard based ratis metrics and export them directly to the /prom http endpoint (used by ozone insight and ratis).
> Unfortunately Dropwizard is very simple, there is no tag support. All of the instance specific strings are part of the metric name. For example:
> {code:java}
> "ratis_grpc.log_appender.72caaf3a-fb1c-4da4-9cc0-a2ce21bb8e67@group"
> + "-72caaf3a-fb1c-4da4-9cc0-a2ce21bb8e67"
> + ".grpc_log_appender_follower_75fa730a-59f0-4547"
> + "-bd68-216162c263eb_latency", {code}
> In this patch I will use a simple method: during the export of the dropwizard metrics based on the well known format of the ratis metrics, they are converted to proper prometheus metrics where the instance information is included as tags:
> {code:java}
> ratis_grpc.log_appender.grpc_log_appender_follower_latency{instance="72caaf3a-fb1c-4da4-9cc0-a2ce21bb8e67"}
> {code}
> With this approach we can:
> 1. monitor easily all the Ratis pipelines with one simple query
> 2. Use the metrics for ozone insight which will show health state of the Ratis pipeline
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org