[
https://issues.apache.org/jira/browse/HBASE-25002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ramkrishna.s.vasudevan updated HBASE-25002:
---
Description:
Currently we allow querying a metric with a specific metric name. But generally
say under the MBean sub=Tables under a server we might have 'n' number of
tables and we might be interested in a specific metric across all tables.
So in such cases giving a simple pattern based query will help so that we can
retrieve all metrics that follow that pattern.
The other side effect is that we can also reduce the size of the json we pull
from the server to the querying client. Which are generally smaller scripts
which might not be able to process the big sized response JSON.
Thanks [~anoopsamjohn] for the suggestion.
was:
Currently we allow querying a metric with a specific metric name. But generally
say under the MBean sub=Tables under a server we might have 'n' number of
tables and we might be interested in a specific metric across all tables.
So in such cases giving a simple pattern based query will help so that we can
retrieve all metrics that follow that pattern.
The other side effect is that we can also reduce the size of the json we pull
from the server to the querying client. Which are generally smaller scripts
which might not be able to process the big sized response JSON.
> Create simple pattern matching query for retrieving metrics matching the
> pattern
>
>
> Key: HBASE-25002
> URL: https://issues.apache.org/jira/browse/HBASE-25002
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 2.2.5
>Reporter: ramkrishna.s.vasudevan
>Assignee: ramkrishna.s.vasudevan
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.3, 2.4.0, 2.2.6
>
>
> Currently we allow querying a metric with a specific metric name. But
> generally say under the MBean sub=Tables under a server we might have 'n'
> number of tables and we might be interested in a specific metric across all
> tables.
> So in such cases giving a simple pattern based query will help so that we can
> retrieve all metrics that follow that pattern.
> The other side effect is that we can also reduce the size of the json we pull
> from the server to the querying client. Which are generally smaller scripts
> which might not be able to process the big sized response JSON.
> Thanks [~anoopsamjohn] for the suggestion.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
