[jira] [Resolved] (KAFKA-19882) JMX tags applied to all client metrics, not just client state for KIP-1091

["Bill Bejeck (Jira)" <ji...@apache.org>]

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

Bill Bejeck resolved KAFKA-19882.
---------------------------------
    Resolution: Fixed

> JMX tags applied to all client metrics, not just client state for KIP-1091
> --------------------------------------------------------------------------
>
>                 Key: KAFKA-19882
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19882
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 4.0.0
>            Reporter: Bill Bejeck
>            Assignee: Genseric Ghiro
>            Priority: Major
>             Fix For: 4.2.0, 4.0.2, 4.1.2
>
>
> When working on [KIP-1091|https://cwiki.apache.org/confluence/display/KAFKA/KIP-1091%3A+Improved+Kafka+Streams+operator+metrics], we mistakenly applied the `process-id` tag to all client-level metrics, rather than just the `client-state`, `thread-state`, and `recording-level` metrics as specified in the KIP.  This issue came to light while working on KIP-1221, which aimed to add the `application-id` as a tag to the `client-state` metric introduced by KIP-1091.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)