[
https://issues.apache.org/jira/browse/ZOOKEEPER-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16547844#comment-16547844
]
Robert Joseph Evans commented on ZOOKEEPER-3092:
------------------------------------------------
+1 This is something that I had a customer ask for just yesterday. I love the
service loader idea, or something that can keep the classpath unchanged unless
someone wants to use it.
One thing to keep in mind too is that a lot of metrics systems, like
codahale/dropwizard, do not support dimensions. It is especially helpful if
you want to do something slightly more advanced like showing a breakdown of
load by user or connections by the host they are coming from. This is not
something I think we have to have up front, but there are use cases where it
can be very helpful. Flink forked dropwizard to be able to support them.
Hadoop metrics2 has this in there too as context. For storm this is something
that I am battling with right now because we opted for just using pure
dropwizard and are regretting it. Please learn from my mistakes.
> 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)
