Versions Compared

Key

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

...

  • If you just have timeline.metrics.whitelist.file = <some_file>, only metrics in that file will be allowed (irrespective of whatever apps might be sending them). 
  • If you just have timeline.metrics.apps.blacklist = datanode, all datanode metrics will be disallowed. Metrics from all other services will be allowed.
  • If you just have timeline.metrics.apps.whitelist = namenode, it is not useful since there is no blacklisting at all. 
  • If you have metric whitelisting enabled (through a file), and have timeline.metrics.apps.blacklist = datanode, all datanode metrics will be disallowed. The whitelisted metrics from other services will be allowed.
  • If you have timeline.metrics.apps.blacklist = datanode, timeline.metrics.apps.whitelist = namenode and metric whitelisting enabled (through a file), datanode metrics will be blacklisted, all namenode metrics will be allowed, and whitelisted metrics from other services will be allowed.

Known Issues

  1. Jira
    serverASF JIRA
    serverId5aa69414-a9e9-3523-82ec-879b028fb15b
    keyAMBARI-25383
    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 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