[
https://issues.apache.org/jira/browse/HBASE-9774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988026#comment-15988026
]
Enis Soztutar commented on HBASE-9774:
--------------------------------------
bq. As HBase is moving away from Hadoop's metric2, I think this patch is a
good start to have HBase specific independent metrics.
Makes sense. We should start using this lib inside HBase.
bq. Do you have plans/ thoughts on how metrics description can be made
available to user?
I don't think the dropwizard API supports the metric descriptions thats why it
is not there in our API as well. Not sure how useful the metric descriptions
are.
> HBase native metrics and metric collection for coprocessors
> -----------------------------------------------------------
>
> Key: HBASE-9774
> URL: https://issues.apache.org/jira/browse/HBASE-9774
> Project: HBase
> Issue Type: New Feature
> Components: Coprocessors, metrics
> Reporter: Gary Helmling
> Assignee: Enis Soztutar
> Fix For: 2.0.0
>
> Attachments: hbase-9774_v1.patch, hbase-9774_v3.patch,
> hbase-9774_v4.patch, hbase-9774_v5.patch
>
>
> It would help provide better visibility into what coprocessors are doing if
> we provided a way for coprocessors to export their own metrics. The general
> idea is to:
> * extend access to the HBase "metrics bus" down into the coprocessor
> environments
> * coprocessors can then register and increment custom metrics
> * coprocessor metrics are then reported along with all others through normal
> mechanisms
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
