[
https://issues.apache.org/jira/browse/HBASE-15519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16936303#comment-16936303
]
Ankit Singhal commented on HBASE-15519:
---------------------------------------
{quote}Pardon the potentially ignorant question. I'm on vacation with just a
phone. Does this work include exporting at least a subset of per user accouting
in ClusterStatus? It would be fine to do this as a follow up of course. Reason
I ask is hbtop receives its telemetry from ClusterStatus and an obvious and
important enhancement for that tool would be a display mode for top N user or
top N client activity by server or region (or table or namespace aggregates).
{quote}
sorry for the late response, currently these metrics are not added in
clusterMetrics/ServerMetrics but we can add them. I see you created HBASE-23065
, so let me take up that and work on it.
And also LossyCounting keeps metrics for those users only which are active(and
new) and trim others, which help in saving some network while transferring them
and make more sense for topN user or topN client use-case as well (though have
importance at a point in time only).
> Add per-user metrics
> ---------------------
>
> Key: HBASE-15519
> URL: https://issues.apache.org/jira/browse/HBASE-15519
> Project: HBase
> Issue Type: Sub-task
> Components: metrics
> Affects Versions: 1.2.0
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Priority: Major
> Attachments: HBASE-15519.master.003.patch, hbase-15519_v0.patch,
> hbase-15519_v1.patch, hbase-15519_v1.patch, hbase-15519_v2.patch
>
>
> Per-user metrics will be useful in multi-tenant cases where we can emit
> number of requests, operations, num RPCs etc at the per-user aggregate level
> per regionserver. We currently have throttles per user, but no way to monitor
> resource usage per-user.
> Looking at these metrics, operators can adjust throttles, do capacity
> planning, etc per-user.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
