[ https://issues.apache.org/jira/browse/ROCKETMQ-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156354#comment-16156354 ]
ASF GitHub Bot commented on ROCKETMQ-271: ----------------------------------------- Github user coveralls commented on the issue: https://github.com/apache/incubator-rocketmq/pull/156 [![Coverage Status](https://coveralls.io/builds/13160524/badge)](https://coveralls.io/builds/13160524) Coverage decreased (-1.6%) to 37.152% when pulling **9f6ead962c510c69b5a29480e040a84d751aebf8 on fuyou001:ROCKETMQ-271** into **368e7c86a0b06099f336c81672112dcb5143cf9e on apache:develop**. > add diagnosis tools > ------------------- > > Key: ROCKETMQ-271 > URL: https://issues.apache.org/jira/browse/ROCKETMQ-271 > Project: Apache RocketMQ > Issue Type: New Feature > Components: rocketmq-broker, rocketmq-client, rocketmq-commons, > rocketmq-remoting > Reporter: yubaofu > Assignee: yukon > Priority: Minor > Original Estimate: 96h > Remaining Estimate: 96h > > when prodcurer send message timeout,how to find the root cause,it's difficult. > so add the new diagnosis tools that record message lifetime ,eg message > create time,prodcurer send message to broker time,broker recive message > time,and send response to client time. -- This message was sent by Atlassian JIRA (v6.4.14#64029)