[
https://issues.apache.org/jira/browse/KAFKA-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377364#comment-16377364
]
Navina Ramesh commented on KAFKA-6588:
--------------------------------------
[~wushujames] `time-since-last-run-ms` is a useful metric. However, it does not
directly indicate the health of the cleaner thread. In the past, we relied on
`max-dirty-ratio` for setting up alerts. The problem with both these metrics is
that it is hard to tune the alerting thresholds, esp. when there are topics
with varying loads. Eventually, these just became noise more than alert. Hence,
we decided to add a more direct metric for monitoring the log cleaner thread,
instead of relying on indirect metrics.
> Add a metric to monitor live log cleaner thread
> -----------------------------------------------
>
> Key: KAFKA-6588
> URL: https://issues.apache.org/jira/browse/KAFKA-6588
> Project: Kafka
> Issue Type: Bug
> Reporter: Navina Ramesh
> Assignee: Navina Ramesh
> Priority: Minor
>
> We want to have a more direct metric to monitor the log cleaner thread.
> Hence, adding a simple metric in `LogCleaner.scala`.
> Additionally, making a minor change to make sure the correct offsets are
> logged in `LogCleaner#recordStats`
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
