[
https://issues.apache.org/jira/browse/KAFKA-16567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839225#comment-17839225
]
Walter Hernandez commented on KAFKA-16567:
------------------------------------------
I noticed that KIP-869 not only introduced these metrics, but also referred to
the deprecation of another metric (KAFKA-16336).
Since KAFKA-16336 was a blocker, I assumed that this fell in that category, but
I see that KAFKA-16336 is a subtasks of a larger ticket (and thus is a blocker
for the main task?).
What would be a moreappropriate Priority for this?
> 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
> Assignee: 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)
