[
https://issues.apache.org/jira/browse/KAFKA-8470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17063428#comment-17063428
]
ASF GitHub Bot commented on KAFKA-8470:
---------------------------------------
stanislavkozlovski commented on pull request #8320:
KAFKA-8470-state-change-logger
URL: https://github.com/apache/kafka/pull/8320
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, it seems better to change the
default level to INFO and move the logs we consider useful to that level.
----------------------------------------------------------------
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
(v8.3.4#803005)
