Page History

...

Two new configurations will be introduce to allow filtering the set of metrics exposed via JMX on brokers and clients.

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

...

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

By default, this would not change the set of metrics exposed via JMX: all metrics would be exposed.

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.

Brokers specifics:

• Configurations will apply to JMX metrics exposed via Yammer metrics as well Kafka's internal metrics library.

• Configurations will be marked as dynamic to allow updates at runtime

...

• : adding and removing JMX metrics as needed to reflect the new filters.

For clientsClients, 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 metrics library.

By default, this would not change the set of metrics exposed via JMX: all metrics would be exposed.

...

• .

Example

To hide log-level metrics LogEndOffset, LogStartOffset, and NumLogSegments, as well as any partition level metrics, except  UnderMinIsr, one could exclude those by specifying the following property in their server.properties file:

...