Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 171EC18D3C for ; Tue, 19 Apr 2016 00:11:26 +0000 (UTC) Received: (qmail 71461 invoked by uid 500); 19 Apr 2016 00:11:25 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 71403 invoked by uid 500); 19 Apr 2016 00:11:25 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 71343 invoked by uid 99); 19 Apr 2016 00:11:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Apr 2016 00:11:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 9FD332C1F68 for ; Tue, 19 Apr 2016 00:11:25 +0000 (UTC) Date: Tue, 19 Apr 2016 00:11:25 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (HBASE-15614) Report metrics from JvmPauseMonitor MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-15614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15246803#comment-15246803 ] Andrew Purtell edited comment on HBASE-15614 at 4/19/16 12:10 AM: ------------------------------------------------------------------ bq. I'm thinking about whether tcollector would automatically pick up the new metric. Yes, there will be two new counters and two new histograms included in the server source metrics, that will be transmitted/processed with the rest. Any existing setup to record server source metrics will get them. was (Author: apurtell): bq. I'm thinking about whether tcollector would automatically pick up the new metric. Yes, there will be two new counters and two new histograms included in the server source metrics, that will be transmitted/processed with the rest. > 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-0.98.patch, HBASE-15614.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)