[
https://issues.apache.org/jira/browse/KAFKA-14953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17739655#comment-17739655
]
Jorge Esteban Quilcate Otoya commented on KAFKA-14953:
------------------------------------------------------
I also find confusing the semantics of `RemoteBytesIn|Out`:
In regular Kafka, BytesIn means bytes written to the log, and BytesOut are
bytes read from the log; but with TS:
* RemoteBytesIn means "Number of bytes read from remote storage per second."
and
* RemoteBytesOut means "Number of bytes copied to remote storage per second."
which is the opposite.
Would it make sense to align these metric names?
Another option may be to not trying to reuse the names, and use more specific
metric names: "RemoteCopyBytes", "RemoteFetchBytes" instead?
> Add metrics for tiered storage
> ------------------------------
>
> Key: KAFKA-14953
> URL: https://issues.apache.org/jira/browse/KAFKA-14953
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Divij Vaidya
> Assignee: Abhijeet Kumar
> Priority: Minor
>
> Not just for expired fetch. We also need to add all the metrics described in
> KIP-405
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-405%3A+Kafka+Tiered+Storage#KIP405:KafkaTieredStorage-NewMetrics
>
> ref: [https://github.com/apache/kafka/pull/13535#discussion_r1180286031]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
