[
https://issues.apache.org/jira/browse/KAFKA-16567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839907#comment-17839907
]
Matthias J. Sax commented on KAFKA-16567:
-----------------------------------------
Thanks Bruno – makes sense to me – should we move K16336 out of the 4.0 ticket,
and into the 5.0 one? If we enable state updater in 3.8, it need to honor our
deprecation period and can only remove the metrics in 5.0, right?
For this ticket, it'll link it to the KIP and update it accordingly. It's not a
blocker for 4.0.
> Add New Stream Metrics based on KIP-869
> ---------------------------------------
>
> Key: KAFKA-16567
> URL: https://issues.apache.org/jira/browse/KAFKA-16567
> Project: Kafka
> Issue Type: Task
> Components: streams
> Reporter: Walter Hernandez
> Priority: Blocker
> Labels: kip
> Fix For: 4.0.0
>
>
> Add the following metrics to the state updater:
> * restoring-active-tasks: count
> * restoring-standby-tasks: count
> * paused-active-tasks: count
> * paused-standby-tasks: count
> * idle-ratio: percentage
> * restore-ratio: percentage
> * checkpoint-ratio: percentage
> * restore-records-total: count
> * restore-records-rate: rate
> * restore-call-rate: rate
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
