[
https://issues.apache.org/jira/browse/HBASE-15614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15246790#comment-15246790
]
Nick Dimiduk commented on HBASE-15614:
--------------------------------------
bq. I kind of like the idea of mixing this in to the server sources, so the
pause metrics appear in their JMX hierarchy, but could also make this
standalone like MetricsWAL. Any preference?
Mixed in with the other server-level metrics makes sense to me. How would that
impact its use for consumers? I'm thinking about whether tcollector would
automatically pick up the new metric.
> Report metrics from JvmPauseMonitor
> -----------------------------------
>
> Key: HBASE-15614
> URL: https://issues.apache.org/jira/browse/HBASE-15614
> Project: HBase
> Issue Type: Improvement
> Components: metrics, regionserver
> Reporter: Nick Dimiduk
> Assignee: Andrew Purtell
> Fix For: 2.0.0, 1.3.0, 0.98.19
>
> Attachments: HBASE-15614-0.98.patch, HBASE-15614.patch,
> HBASE-15614.patch, HBASE-15614.patch
>
>
> We have {{JvmPauseMonitor}} for detecting JVM pauses; pauses are logged at
> WARN. Would also be good to expose this information on a dashboard via
> metrics system -- make it easier to get this info off the host and into a
> central location for the operator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
