[
https://issues.apache.org/jira/browse/KUDU-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16835388#comment-16835388
]
HeLifu edited comment on KUDU-2797 at 5/8/19 7:44 AM:
------------------------------------------------------
Right now we collect these metrics via HTTP interface from all of the tservers,
merge and display on the monitoring systems, but it's not friendly for
kudu-users. So i think it's valuable to support it and I'd like to have a try ;)
was (Author: helifu):
Right now we collect these metrics via HTTP interface from all of the tservers,
merge and display on the monitoring systems. But it's not friendly for
kudu-users, i think.
> Implement table size metrics
> ----------------------------
>
> Key: KUDU-2797
> URL: https://issues.apache.org/jira/browse/KUDU-2797
> Project: Kudu
> Issue Type: Task
> Components: master, metrics
> Affects Versions: 1.8.0
> Reporter: Mike Percy
> Assignee: HeLifu
> Priority: Major
>
> It would be valuable to implement table size metrics for row count and byte
> size (pre-replication and post-replication). The master could aggregate these
> stats from the various partitions (tablets) and expose aggregated metrics for
> consumption by monitoring systems and dashboards. These same metrics would
> also be valuable to display on the web UI.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
