Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • App Blacklisting - Blacklist metrics from one or more services. Other service metrics will be entirely allowed or controlled through a whitelist file. 
    ams-site : timeline.metrics.apps.blacklist = hbase,namenode


  • App Whitelisting - Whitelist metrics from one or more services.
     ams-site:timeline.metrics.apps.whitelist = nimbus,datanode      

...

  1. The Kafka Topics Grafana dashboard is unable to discover the Kafka Topics by default if whitelisting is enabled. The reason is that 'kafka.log.Log.*' metrics are used to filter the available Kafka Topics but those metrics are not enabled by default in the whitelist file. The issue can be remediated by adding '._p_kafka.log.Log.*' to the whitelist file and restarting the Metrics Collector.
    Jira
    serverASF JIRA
    serverId5aa69414-a9e9-3523-82ec-879b028fb15b
    keyAMBARI-25383

  2. The following metrics are erroneously filtered by the whitelisting despite they are defined whitelist file. Due to this issue the Kafka Topics Grafana dashboard is not showing data.
    kafka.server.BrokerTopicMetrics.BytesInPerSec.topic.*.count
    kafka.server.BrokerTopicMetrics.BytesOutPerSec.topic.*.count
    kafka.server.BrokerTopicMetrics.MessagesInPerSec.topic.*.count
    kafka.server.BrokerTopicMetrics.TotalProduceRequestsPerSec.topic.*.
    countThe
    count
    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 .
    Jira
    serverASF JIRA
    serverId5aa69414-a9e9-3523-82ec-879b028fb15b
    keyAMBARI-25383