[ https://issues.apache.org/jira/browse/HBASE-22407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Duo Zhang updated HBASE-22407: ------------------------------ Status: Open (was: Patch Available) > add an option to use Hadoop metrics tags for table metrics (and fix some > issues in metrics) > ------------------------------------------------------------------------------------------- > > Key: HBASE-22407 > URL: https://issues.apache.org/jira/browse/HBASE-22407 > Project: HBase > Issue Type: Bug > Reporter: Sergey Shelukhin > Assignee: Sergey Shelukhin > Priority: Major > Attachments: HBASE-22407.01.patch > > > Currently table metrics are output using custom metrics names that clutter > various metrics lists and are impossible to (sanely) aggregate. > We can use Hadoop MetricsTag to instead use tagging on a single metric (for a > given logical metric), allowing both per-table display and cross-table > aggregation on the other end. > In this JIRA (patch coming) I'd like to add the ability to do that > 1) Actual tagging in multiple paths that output table metrics. > 2) The ugliest part - preventing server-level metrics from being output in > tags case to avoid duplicate metrics. Seems like a large refactor of the > metrics is in order (not included)... > 3) Fixes for some issues where wrong metrics are output, metrics are not > output at all, exceptions like null Optional cause table metrics to not be > output forever, etc. > 4) Renaming several table-level latency metrics to be consistent with > server-level latency metrics. -- This message was sent by Atlassian JIRA (v7.6.14#76016)