[
https://issues.apache.org/jira/browse/KAFKA-8470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855476#comment-16855476
]
ASF GitHub Bot commented on KAFKA-8470:
---------------------------------------
stanislavkozlovski commented on pull request #6878: KAFKA-8470: State change
logs should not be in TRACE level
URL: https://github.com/apache/kafka/pull/6878
The StateChange logger in Kafka should not be logging its state changes in
TRACE level.
We consider these changes very useful in debugging. Given that we configure
that logger to log in TRACE levels by default, we obviously deem it important.
Let's have these logs be in INFO and unlock the use of a proper TRACE level log
down the line
https://issues.apache.org/jira/browse/KAFKA-8470
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> State change logs should not be in TRACE level
> ----------------------------------------------
>
> Key: KAFKA-8470
> URL: https://issues.apache.org/jira/browse/KAFKA-8470
> Project: Kafka
> Issue Type: Improvement
> Reporter: Stanislav Kozlovski
> Assignee: Stanislav Kozlovski
> Priority: Minor
>
> The StateChange logger in Kafka should not be logging its state changes in
> TRACE level.
> We consider these changes very useful in debugging and we additionally
> configure that logger to log in TRACE levels by default.
> Since we consider it important enough to configure its own logger to log in a
> separate log level, why don't we change those logs to INFO and have the
> logger use the defaults?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
