Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 3D447200BAD for ; Mon, 10 Oct 2016 19:24:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3C28D160AD1; Mon, 10 Oct 2016 17:24:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B25E9160AE1 for ; Mon, 10 Oct 2016 19:24:21 +0200 (CEST) Received: (qmail 97363 invoked by uid 500); 10 Oct 2016 17:24:20 -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 97334 invoked by uid 99); 10 Oct 2016 17:24:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Oct 2016 17:24:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 874F92C0B04 for ; Mon, 10 Oct 2016 17:24:20 +0000 (UTC) Date: Mon, 10 Oct 2016 17:24:20 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-16800) Support for smart querying of our published jmx per server over http+json MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 10 Oct 2016 17:24:22 -0000 [ https://issues.apache.org/jira/browse/HBASE-16800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-16800: -------------------------- Attachment: HBASE-16800.master.001.patch > Support for smart querying of our published jmx per server over http+json > ------------------------------------------------------------------------- > > Key: HBASE-16800 > URL: https://issues.apache.org/jira/browse/HBASE-16800 > Project: HBase > Issue Type: Improvement > Components: metrics > Reporter: stack > Assignee: stack > Attachments: HBASE-16800.master.001.patch, HBASE-16800.master.002.patch > > > We currently expose our jmx metrics via a json dump in a servlet at /jmx. You get all or nothing (You can add a '?description=true' to get a description for each metric published but that is it). > A means of being able to query by metric or by a set of metrics would make graphing easier to do, especially over http dumping json. In particular, our [~appy] is trying to put up pages that give insight into current state of replication. > Related, HBASE-11747 ClusterStatus is too bulky, is about how whenever we need a metric 'exposed', our only means is by bulking out the heartbeat adding payload on each message we send the server (In the issue, w/ 1M regions, each RS is sending 100MB of 'status' every second). We need to undo metrics collection from clusterstatus function > Bonus if able to compress/cache payloads, security, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)