[
https://issues.apache.org/jira/browse/ZOOKEEPER-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16547358#comment-16547358
]
Michael Han commented on ZOOKEEPER-3092:
----------------------------------------
bq. If there is no hurry I can pick this up.
Great.
bq. But in order to start we have to decide which are the metrics to expose.
If you mean the type of metrics, I think as a start, we can define the most
useful types: counter, gauge, and stats (time series data). Later maybe we can
add histogram or something more complicated. We need define the interface of
the metric system that allows get/set of these metrics types, and then provide
some default implementations. The system should allow an external library that
implements the same interface to load at runtime (thus called pluggable).
Once the interface and default implementation is ready, we can start instrument
the code base to collect various metrics.
> Pluggable metrics system for ZooKeeper
> --------------------------------------
>
> Key: ZOOKEEPER-3092
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3092
> Project: ZooKeeper
> Issue Type: New Feature
> Components: metric system
> Reporter: Michael Han
> Priority: Major
>
> ZooKeeper should provide a pluggable metrics system such that various metrics
> can be collected and reported using different approaches that fit production
> monitoring / alert / debugging needs.
> Historically ZooKeeper provides four letter words and JMX which exposes
> certain stats / metrics but they are not very flexible in terms of
> programmatically accessing metrics and connecting metrics to different
> reporting systems.
> There are other projects that's already doing this which can be used for
> reference, such as bookkeeper metrics service providers and hadoop metrics2.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
