[jira] [Updated] (AMBARI-25394) Ambari Metrics whitelisting is failing on * wildcard for HBASE Tables

["Szilard Antal (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMBARI-25394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Szilard Antal updated AMBARI-25394:
-----------------------------------
    Summary: Ambari Metrics whitelisting is failing on * wildcard for HBASE Tables  (was: Ambari Metrics whitelisting is failing on * wildcard for HBASE Tables metrics)

> Ambari Metrics whitelisting is failing on * wildcard for HBASE Tables
> ---------------------------------------------------------------------
>
>                 Key: AMBARI-25394
>                 URL: https://issues.apache.org/jira/browse/AMBARI-25394
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-metrics
>    Affects Versions: 2.6.0, 2.6.1, 2.6.2, 2.7.3, 2.7.4
>            Reporter: Szilard Antal
>            Assignee: Szilard Antal
>            Priority: Major
>              Labels: grafana, hbase, metrics
>             Fix For: 2.7.5
>
>
> On Ambari 2.6.x and 2.7.x if the Ambari Metrics Collector whitelisting is enabled, nothing appears in the Grafana HBase - Tables/Users dashboards.
> The related metric-patterns are enabled in the whitelist file but it seems that the metrics matching with these patterns are filtered out and not shown on Grafana dashboard.
> eg:
> {code:java}
> regionserver.Tables.*_metric_storeCount
> regionserver.Tables.*_metric_storeFileCount
> regionserver.Tables.*_metric_storeFileSize
> regionserver.Tables.*_metric_tableSize
> regionserver.Tables.*_metric_totalRequestCount
> regionserver.Tables.*_metric_writeRequestCount
> regionserver.Users.*_metric_append_num_ops
> regionserver.Users.*_metric_delete_num_ops{code}
> To fix this the ._p_ prefix should be ​​added to the above prefixes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)