[ 
https://issues.apache.org/jira/browse/KAFKA-8874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938296#comment-16938296
 ] 

ASF GitHub Bot commented on KAFKA-8874:
---------------------------------------

KevinLiLu commented on pull request #7395: [WIP] KAFKA-8874: Add consumer 
metrics to observe user poll behavior
URL: https://github.com/apache/kafka/pull/7395
 
 
   **NOT READY TO MERGE**
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> KIP-517: Add consumer metric indicating time between poll calls
> ---------------------------------------------------------------
>
>                 Key: KAFKA-8874
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8874
>             Project: Kafka
>          Issue Type: New Feature
>          Components: consumer, metrics
>            Reporter: Kevin Lu
>            Assignee: Kevin Lu
>            Priority: Minor
>
> [https://cwiki.apache.org/confluence/display/KAFKA/KIP-517%3A+Add+consumer+metric+indicating+time+between+poll+calls]
> It would be beneficial to add a metric to record the average/max time between 
> calls to poll as it can be used by both Kafka application owners and 
> operators to:
>  * Easily identify if/when max.poll.interval.ms needs to be changed (and to 
> what value)
>  * View trends/patterns
>  * Verify max.poll.interval.ms was hit using the max metric when debugging 
> consumption issues (if logs are not available)
>  * Configure alerts to notify when average/max time is too close to 
> max.poll.interval.ms



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to