[
https://issues.apache.org/jira/browse/KAFKA-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002470#comment-15002470
]
Gwen Shapira commented on KAFKA-2820:
-------------------------------------
While we are there, SASL has its own debug flag:
-Dsun.security.krb5.debug=true
Will be awesome to have this in the logs where running SASL tests at debug
level.
> System tests: log level is no longer propagating from service classes
> ---------------------------------------------------------------------
>
> Key: KAFKA-2820
> URL: https://issues.apache.org/jira/browse/KAFKA-2820
> Project: Kafka
> Issue Type: Bug
> Reporter: Geoff Anderson
>
> Many system test service classes specify a log level which should be
> reflected in the log4j output of the corresponding kafka tools etc.
> However, these log levels are no longer propagating, which makes tests much
> harder to debug after they have run.
> E.g. KafkaService specifies a DEBUG log level, but all collected log output
> from brokers is at INFO level or above.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
