[AMBARI-25383] Ambari Metrics whitelisting is failing on * wildcard for Kafka Topics

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.0, 2.6.1, 2.6.2, 2.7.3, 2.7.4
• Fix Version/s: 2.8.0, 2.7.5
• Component/s: ambari-metrics
• Labels: grafana kafka metrics pull-request-available
• Assignee: Szilárd Antal
• Reporter: Tamas Payer
• Created: 24/Sep/19 11:39
• Updated: 17/Nov/22 09:36
• Resolved: 14/Oct/19 11:46

Description

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:

kafka.server.BrokerTopicMetrics.BytesInPerSec.topic.*.count
kafka.server.BrokerTopicMetrics.BytesOutPerSec.topic.*.count
kafka.server.BrokerTopicMetrics.MessagesInPerSec.topic.*.count
kafka.server.BrokerTopicMetrics.TotalProduceRequestsPerSec.topic.*.count

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 .

Issue Links

• links to: GitHub Pull Request #64
• links to: GitHub Pull Request #3095
• mentioned in: Page Loading...