[
https://issues.apache.org/jira/browse/HDDS-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-2300:
---------------------------------
Labels: pull-request-available (was: )
> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
