[
https://issues.apache.org/jira/browse/KAFKA-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-1250:
-----------------------------
Attachment: kafka_trace.txt
kafka_debug.txt
Okay guys, I have capitulated on the config logging thing. I really think this
is a nasty inelegant thing to do and we should not do it, but I think we need
to make progress.
Since it sounds like people weren't actually looking at logging output but
rather just spot checking log statements. I think it is hard to get a sense of
the output this way. I think the more important thing is to look at the logging
output. To help people do this I have included the output at TRACE and DEBUG
levels.
The general idea is that this should tell the rough story of what has
transpired. One can always log more but I think adding lower value log
statements actually is a net negative as it obscures more important things.
At a high level I am following the logging guidelines in the coding standard
but with the assumption that in the client what the client generally wants is
the response or exception and logging is more of a tracing facility.
> Add slf4j logging to new producer
> ---------------------------------
>
> Key: KAFKA-1250
> URL: https://issues.apache.org/jira/browse/KAFKA-1250
> Project: Kafka
> Issue Type: Sub-task
> Components: producer
> Reporter: Jay Kreps
> Assignee: Jay Kreps
> Attachments: KAFKA-1250.patch, KAFKA-1250_2014-02-25_21:31:44.patch,
> KAFKA-1250_2014-02-26_18:32:24.patch, kafka_debug.txt, kafka_trace.txt
>
>
> Currently there is no logging in the client.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
