Page History

...

The configurations would apply to brokers, as well as clients, streams, and connect.

On the broker, the configurations will also be marked as dynamic to allow updates at runtime.

The following configs will be introduced for brokers, 

metrics.jmx.whitelist=<regular expression of mbeans to expose> (defaults to ".*")

metrics.jmx.blacklist=<regular expression of mbeans to hide> (defaults to "", takes precedence over the whitelist)

These On the broker, the configurations will also be marked as dynamic to allow updates at runtime. Dynamic updates would both add and remove JMX metrics as needed to reflect the new filters.

For clients, streams, and connect:

Configuration will apply to all the metrics exposed in JMX metrics via Kafka's internal metrics library.

For Brokers

Configurations will apply to JMX metrics exposed via both Yammer metrics as well Kafka's internal apply to both JMX metrics exposed via Yammer metrics (only applies to brokers) as well as JMX metrics exposed via Kafka's own metrics library.

By default, this would not change the set of metrics exposed via JMX: all metrics would be exposed.On the broker, updates to the configurations at runtime would both add and remove JMX metrics as needed to reflect the new filters.

All metrics continue to be collected in the background regardless of those settings, so this only affects the visibility in JMX and not the actual metric values.

...