You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2019/10/22 09:32:00 UTC

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

    [ https://issues.apache.org/jira/browse/AMBARI-25394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956859#comment-16956859 ] 

Hudson commented on AMBARI-25394:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #593 (See [https://builds.apache.org/job/Ambari-branch-2.7/593/])
AMBARI-25394 Ambari Metrics whitelisting is failing on * wildcard for (dlysnichenko: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=fd305e7de5a18002102e7cec8c717289b33bb1fe])
* (edit) ambari-metrics/ambari-metrics-timelineservice/conf/unix/metrics_whitelist


> 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, pull-request-available
>             Fix For: 2.7.5
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> 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)