[ https://issues.apache.org/jira/browse/KAFKA-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126641#comment-14126641 ]
Abhishek Sharma commented on KAFKA-1590: ---------------------------------------- Right now we are using log4j for logging in Kafka. Binary logging format is not supported in log4j. We can have two options - 1) We can write log4j Custom Appender that extends AppenderSkeleton for supporting binary logging format 2) Explore some alternative for binary logging like mfz-binlog (https://code.google.com/p/mfz-binlog/). [~guozhang] - Is there any other option? Any suggestion over this? > Binarize trace level request logging along with debug level text logging > ------------------------------------------------------------------------ > > Key: KAFKA-1590 > URL: https://issues.apache.org/jira/browse/KAFKA-1590 > Project: Kafka > Issue Type: Bug > Reporter: Guozhang Wang > Labels: newbie > Fix For: 0.9.0 > > > With trace level logging, the request handling logs can grow very fast > depending on the client behavior (e.g. consumer with 0 maxWait and hence keep > sending fetch requests). Previously we have changed it to debug level which > only provides a summary of the requests, omitting request details. However > this does not work perfectly since summaries are not sufficient for > trouble-shooting, and turning on trace level upon issues will be too late. > The proposed solution here, is to default to debug level logging with trace > level logging printed as binary format at the same time. The generated binary > files can then be further compressed / rolled out. When needed, we will then > decompress / parse the trace logs into texts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)