You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Yining Liu (JIRA)" <ji...@apache.org> on 2019/02/21 08:27:00 UTC

[jira] [Updated] (KAFKA-7942) Monitoring consumer lag by timestamp

     [ https://issues.apache.org/jira/browse/KAFKA-7942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yining Liu updated KAFKA-7942:
------------------------------
    Summary: Monitoring consumer lag by timestamp  (was: Monitoring consumer lag by time)

> Monitoring consumer lag by timestamp
> ------------------------------------
>
>                 Key: KAFKA-7942
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7942
>             Project: Kafka
>          Issue Type: Wish
>          Components: consumer, metrics
>            Reporter: Yining Liu
>            Priority: Major
>
> Currently, we can collect num of messages consumer lagging behind producer. However, if messages come into a partition sporadically, we are not easy to define consumer lag alert threshold. If we know how long consumer lagging behind latest message, it must be helpful.
> There are two options:
>  # expose per partition lag time by consumer jmx metrics
>  # expose consumer lag time in kafka-consumer-groups.sh



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)