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

ASF GitHub Bot commented on ROCKETMQ-90:
----------------------------------------

Github user coveralls commented on the issue:

    https://github.com/apache/incubator-rocketmq/pull/56
  
    
    [![Coverage 
Status](https://coveralls.io/builds/10824368/badge)](https://coveralls.io/builds/10824368)
    
    Coverage decreased (-0.2%) to 31.101% when pulling 
**cb8092a5cad021dad05497d9283dc0c5a3cef3bc on lizhanhui:ROCKETMQ-90** into 
**e6aaedcf4d23f95791c51fb510baf369c8b1f5c1 on apache:master**.



> Include client IP per message queue of consumer progress command output
> -----------------------------------------------------------------------
>
>                 Key: ROCKETMQ-90
>                 URL: https://issues.apache.org/jira/browse/ROCKETMQ-90
>             Project: Apache RocketMQ
>          Issue Type: Improvement
>          Components: rocketmq-tools
>    Affects Versions: 4.1.0-incubating
>            Reporter: Zhanhui Li
>            Assignee: Zhanhui Li
>            Priority: Minor
>
> Sometimes we monitor message accumulation which is not caused by traffic 
> surge, instead by buggy application consuming code. If we can quickly figure 
> out IP of which client(s) is experiencing  glitches, it saves much time 
> diagnosing issues.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to