[
https://issues.apache.org/jira/browse/KAFKA-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16354831#comment-16354831
]
Allen Wang commented on KAFKA-6514:
-----------------------------------
[~ijuma] Since we don't change the name of the metric, but just adding a tag,
it shouldn't break existing monitoring system. So I am wondering why a KIP is
still required in this case.
For example, I found that when upgrading to Kafka 0.10, "records-consumed-rate"
metric has an added tag "topic", which makes sense to me.
I would prefer keeping the same metric name since people are already familiar
with it and the name makes sense. It would also have minimal impact on the
storage required on a typical metric aggregation system.
> Add API version as a tag for the RequestsPerSec metric
> ------------------------------------------------------
>
> Key: KAFKA-6514
> URL: https://issues.apache.org/jira/browse/KAFKA-6514
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.0.0
> Reporter: Allen Wang
> Priority: Major
>
> After we upgrade broker to a new version, one important insight is to see how
> many clients have been upgraded so that we can switch the message format when
> most of the clients have also been updated to the new version to minimize the
> performance penalty.
> RequestsPerSec with the version tag will give us that insight.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
