[ https://issues.apache.org/jira/browse/KAFKA-17516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914649#comment-17914649 ]
David Jacot commented on KAFKA-17516: ------------------------------------- Changing target fix version to 4.1 since this is not a blocker and we are past code freeze > Client metrics configuration resources default configs not shown by > kafka-configs.sh > ------------------------------------------------------------------------------------ > > Key: KAFKA-17516 > URL: https://issues.apache.org/jira/browse/KAFKA-17516 > Project: Kafka > Issue Type: Bug > Components: admin > Affects Versions: 3.7.0 > Reporter: Andrew Schofield > Assignee: Andrew Schofield > Priority: Major > Fix For: 4.0.0 > > > KIP-714 introduces client metrics configuration resources for configuring the > set of metrics pushed by clients. The kafka-configs.sh and > kafka-client-metrics.sh tools are used to manipulate them. > When kafka-configs.sh is used to manipulate configurations for other resource > types, such as topics and groups, configuration for which there is no > explicit dynamic value specified have a default which is either part of the > definition of the definition of each config, or inherited from another config > (usually from the broker). > This is not the case currently for client metrics resources, and this is not > intentional. There are defaults for the configurations and they are applied. > It's just that they're not visible using kafka-configs.sh --describe --all > and not returned by the admin API. They should be. > This issue adjusts the handling of the default values so that they are > displayed by this tool. -- This message was sent by Atlassian Jira (v8.20.10#820010)