[
https://issues.apache.org/jira/browse/KAFKA-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-892:
--------------------------------
Description: While troubleshooting a lot of 0.8 issues, what I've seen is
that often times than not, I've wanted the request processing latency breakdown
to be part of the request log. There are of course mbeans to expose this
information, but when you are trying to troubleshoot the root cause of few slow
requests, this is immensely helpful. Currently, we only include request
reception in the request log. We could include both but that would double the
size of the request log. So I'm proposing adding just the request completion
information in the request log. This will not just tell us which request came
into the server, but will also give us a breakdown of where it spent most of
its processing time.
> Change request log to include request completion not handling
> -------------------------------------------------------------
>
> Key: KAFKA-892
> URL: https://issues.apache.org/jira/browse/KAFKA-892
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.8
> Reporter: Neha Narkhede
> Assignee: Neha Narkhede
> Priority: Critical
> Labels: kafka-0.8
>
> While troubleshooting a lot of 0.8 issues, what I've seen is that often times
> than not, I've wanted the request processing latency breakdown to be part of
> the request log. There are of course mbeans to expose this information, but
> when you are trying to troubleshoot the root cause of few slow requests, this
> is immensely helpful. Currently, we only include request reception in the
> request log. We could include both but that would double the size of the
> request log. So I'm proposing adding just the request completion information
> in the request log. This will not just tell us which request came into the
> server, but will also give us a breakdown of where it spent most of its
> processing time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
