You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Andrew Schofield (Jira)" <ji...@apache.org> on 2024/09/10 20:05:00 UTC

[jira] [Updated] (KAFKA-17516) Client metrics configuration resources default configs not shown by kafka-configs.sh

     [ https://issues.apache.org/jira/browse/KAFKA-17516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Schofield updated KAFKA-17516:
-------------------------------------
    Summary: Client metrics configuration resources default configs not shown by kafka-configs.sh  (was: Client metrics configuration resources default configs not shown by Kafka-config.sh)

> 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)