[
https://issues.apache.org/jira/browse/ZOOKEEPER-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16547850#comment-16547850
]
Enrico Olivelli commented on ZOOKEEPER-3092:
--------------------------------------------
It would be great to have the new mavenized layout before start coding this new
API.
Nowadays it is very hard (quite impossible) to have a new separate module, we
will have to mix the new API with zookeeper client and server code.
btw we can start designing the API. It won't be an easy task and it would wait
for 3.6.
I will start taking BookKeeper Stats API as example,
are we sure we do not want to use directly BookKeeper stats API directly ? It
is well and actively maintained, it will be a pity to duplicate the work, and
it will let us start directly with the 'code instrumentation'
> 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)
