You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/13 16:52:00 UTC
[jira] [Resolved] (HBASE-6216) per-request tagging
[ https://issues.apache.org/jira/browse/HBASE-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kyle Purtell resolved HBASE-6216.
----------------------------------------
Assignee: (was: Li Pi)
Resolution: Won't Fix
> per-request tagging
> -------------------
>
> Key: HBASE-6216
> URL: https://issues.apache.org/jira/browse/HBASE-6216
> Project: HBase
> Issue Type: New Feature
> Reporter: Kannan Muthukkaruppan
> Priority: Major
>
> Allow applications to tag individual RPC requests so that metrics exposed by HBase can automatically be collected/aggregated by those tags. This'll be useful for problem diagnosis across various applications-- as it will allow us to correlate HBase metrics (such as data block misses) back to application level tags.
> For example,
> * in some multi-tenancy type use case where many different applications are served out of a single Table or CF, it'll be useful to know the break down of metrics (such as bytes read, data block misses, get/put RPC calls, etc.) by application name (tag).
> * even in a single app environment, the app may want to tag different API calls with different tags even if those calls are to the same CF.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)