[
https://issues.apache.org/jira/browse/AMBARI-25383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-25383:
------------------------------------
Labels: grafana kafka metrics pull-request-available (was: grafana kafka
metrics)
> Ambari Metrics whitelisting is failing on * wildcard for Kafka Topics
> ---------------------------------------------------------------------
>
> Key: AMBARI-25383
> URL: https://issues.apache.org/jira/browse/AMBARI-25383
> 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: Tamas Payer
> Assignee: Tamas Payer
> Priority: Major
> Labels: grafana, kafka, metrics, pull-request-available
>
> On Ambari 2.6.x and 2.7.x if the Ambari Metrics Collector whitelisting is
> enabled, the Kafka Topics are not discovered on the Kafka topics dashboard.
> (The Topics dropdown is empty.)
> It can be remediated by adding '._p_kafka.log.Log.*' to the whitelist file
> and restarting the Metrics Collector.
> Adding the '._p_kafka.log.Log.*' to the whitelist file by default should be
> considered. Also it should be investigated why we need the "._p_" prefix.
> Furthermore, it seems that the metrics enabled in the whitelist file as:
> {code:java}
> kafka.server.BrokerTopicMetrics.BytesInPerSec.topic.*.count
> kafka.server.BrokerTopicMetrics.BytesOutPerSec.topic.*.count
> kafka.server.BrokerTopicMetrics.MessagesInPerSec.topic.*.count
> kafka.server.BrokerTopicMetrics.TotalProduceRequestsPerSec.topic.*.count
> {code}
> are filtered out and not shown on Grafana dashboard.
> The issue can be worked around by adding the '._p_' prefix to the
> corresponding metrics in the whitelist file, e.g.
> ._p_kafka.server.BrokerTopicMetrics.BytesInPerSec.topic.*.count .
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
