[ 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)