You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ratis.apache.org by "Aravindan Vijayan (Jira)" <ji...@apache.org> on 2019/10/16 17:24:00 UTC

[jira] [Updated] (RATIS-683) Organize RatisMetrics and RatisMetricNames into a single class

     [ https://issues.apache.org/jira/browse/RATIS-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aravindan Vijayan updated RATIS-683:
------------------------------------
    Description: 
* Organize RatisMetrics and RatisMetricNames into a single class
It would be good to organize RatisMetrics and RatisMetricNames into a single class. The metrics can be organized like RaftServerConfigKeys and RaftClientConfigKeys so that metrics corresponding to a particular component like Log, Appender can be tracked in a sub class.

* 

  was:It would be good to organize RatisMetrics and RatisMetricNames into a single class. The metrics can be organized like RaftServerConfigKeys and RaftClientConfigKeys so that metrics corresponding to a particular component like Log, Appender can be tracked in a sub class.


> Organize RatisMetrics and RatisMetricNames into a single class
> --------------------------------------------------------------
>
>                 Key: RATIS-683
>                 URL: https://issues.apache.org/jira/browse/RATIS-683
>             Project: Ratis
>          Issue Type: Sub-task
>            Reporter: Lokesh Jain
>            Assignee: Aravindan Vijayan
>            Priority: Major
>
> * Organize RatisMetrics and RatisMetricNames into a single class
> It would be good to organize RatisMetrics and RatisMetricNames into a single class. The metrics can be organized like RaftServerConfigKeys and RaftClientConfigKeys so that metrics corresponding to a particular component like Log, Appender can be tracked in a sub class.
> * 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)