Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Status

Current state: Under DiscussionAccepted

JIRA

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-10199
Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-10575

...

Below summarizes the public API changes in this KIP.

Restoration metrics

All the metrics below would be We propose add metrics both on the thread-level (default reporting level is INFO) as well as on the task level (default reporting level is DEBUG).

Note that we will have separate thread handling restoration procedures, and hence their thread id would be different from stream threads.


Metric Thread-level metric tags are:

  • type=stream-state-updater-metrics
  • clientthread-id=[clientIdthreadId]

Task-level metric tags are:

  • type=stream-task-metrics
  • thread-id=[threadId]

...

  • task-id=[taskId]


The POC implementation of the proposed metrics can be found here: https://github.com/apache/kafka/pull/12391


Metric NameLevel

Type

DescriptionNotes
active-restoring-tasks
thread / INFOcountThe number of active tasks currently undergoing restoration
standby-updating-tasks
thread / INFOcountThe number of active tasks currently undergoing updating
active-paused-tasks
thread / INFOcountThe number of active tasks paused restoring
standby-paused-tasks
thread / INFOcountThe number of standby tasks paused updating
idle-ratio
thread / INFOgauge (percentage)The fraction of time the thread spent on being idleidle-ratio + restore/update-ratio + checkpoint-ratio should be 1
active-restore-ratio
thread / INFOgauge (percentage)The fraction of time the thread spent on restoring active
or
tasksidle-ratio + restore/update-ratio + checkpoint-ratio should be 1;
only one of the restore/update-ratio should be non-zero
standby-update-ratiothread / INFOgauge (percentage)The fraction of time the thread spent on updating standby tasks

idle-ratio + restore/update-ratio + checkpoint-ratio should be 1;

only one of the restore/update-ratio should be non-zero

checkpoint-ratio
thread / INFOgauge (percentage)The fraction of time the thread spent on checkpointing restored progressidle-ratio + restore/update-ratio + checkpoint-ratio should be 1
active
restore-records-
restored-totalcount
rate
thread / INFOrateThe average per-second
The total
number of records restored/updated for
active tasksit is for the lifetime of the streams app, hence ever going 
standby-records-updated-total
all tasks
restore-call-rate
thread / INFOrateThe average per-second number of restore calls triggered
restore-total
task / DEBUGcountThe total number of records
updated
processed during restoration for active
tasks
task
it is for the lifetime of the streams app, hence ever going 
active-records-remaining
countThe number of records remained to be restoredit should be usually declining, and during rebalance it may be jumping up or down
standby-records-remaining
countThe number of records remained to be updatedit could be usually increasing or declining, and during rebalance it may be jumping up or downrecords-restored-rate
the metric would persist even when the task completed restoration, and would be removed only when the task is removed from the thread.
restore-rate
task / DEBUGrateThe average per-second number of records restored for active taskthe metric would drop to zero when the task completed restoration, and would be removed only when the task is removed from the thread.
update-totaltask / DEBUGcountThe total number of records updated for standby tasksame as above
update-ratetask / DEBUGrateThe average per-second number of records
restored for active or
updated for standby
it counts for both active and standby tasks
tasksame as above
restore-remaining-
call-rate
records-total
task / INFOcountThe number of records remained to be restored for active tasks
rateThe average per-second number of restore calls triggered


Along with these new metrics, we would also deprecate the metrics below:

...