[
https://issues.apache.org/jira/browse/RATIS-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16947994#comment-16947994
]
Henrik Hegardt edited comment on RATIS-702 at 10/9/19 8:49 PM:
---------------------------------------------------------------
[~elek] I also hoped that it would be possible to specify what metrics lib one
should use. Like my use case is that I'm running with Dropwizard-metrics 4
which isn't compatible with the current dropwizard-metrics 3. Though looking at
your change support for plugging a different metric implementation library
(ratis provides an API for metrics), may be a another issue.
was (Author: hheg):
[~elek] I also hoped that it would be possible to specify what metrics lib one
should use. Like my use case is that I'm running with Dropwizard-metrics 4
which isn't compatible with the current dropwizard-metrics 3. Though looking at
your change support for plugging a different metric implementation library
(ratis provides an API for metrics), may be a different issue.
> Make metrics reporting implementation pluggable
> -----------------------------------------------
>
> Key: RATIS-702
> URL: https://issues.apache.org/jira/browse/RATIS-702
> Project: Ratis
> Issue Type: Wish
> Components: metrics
> Reporter: Henrik Hegardt
> Assignee: Marton Elek
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It would be really nice if the metrics functionality also was pluggable so
> one could choose how to report metrics.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
