Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

You can do this by adding a new line to your log config (which can be accessed on disk or via the SDC UI under Logs/Log Configuration). This line should start with log4j.logger. and then contain the fully qualified name of the logger (which is usually the class, but you can check the source code to confirm). For example, to enable TRACE level on the Kafka library consumer class (to help diagnose Kafka consumer issues), you can add this line:

log4j.logger.org.apache.kafka.clients.consumer.KafkaConsumer=TRACE

You can do this by adding a new line to your log config (which can be accessed on disk at $SDC_CONF/sdc-log4j.properties or via the SDC UI under Logs/Log Configuration). This line should start with log4j.logger. and then contain the fully qualified name of the logger (which is usually the class, but you can check the source code to confirm). For example, to enable TRACE level on the Kafka library consumer class (to help diagnose Kafka consumer issues), you can add this line:

log4j.logger.org.apache.kafka.clients.consumer.KafkaConsumer=TRACE

You can do this by adding a new line to your log config (which can be accessed on disk at $SDC_CONF/sdc-log4j.properties or via the SDC UI under Logs/Log Configuration). This line should start with log4j.logger. and then contain the fully qualified name of the logger (which is usually the class, but you can check the source code to confirm). For example, to enable TRACE level on the Kafka library consumer class (to help diagnose Kafka consumer issues), you can add this line:

log4j.logger.org.apache.kafka.clients.consumer.KafkaConsumer=TRACE

To log an entire package (ex: everything for the JDBC multi-table origin, which happens to live in package com.streamsets.pipeline.stage.origin.jdbc.table), use a line like this:

log4j.logger.com.streamsets.pipeline.stage.origin.jdbc.table

You can do this by adding a new line to your log config (which can be accessed on disk at $SDC_CONF/sdc-log4j.properties or via the SDC UI under Logs/Log Configuration). This line should start with log4j.logger. and then contain the fully qualified name of the logger (which is usually the class, but you can check the source code to confirm). For example, to enable TRACE level on the Kafka library consumer class (to help diagnose Kafka consumer issues), you can add this line:

log4j.logger.org.apache.kafka.clients.consumer.KafkaConsumer=TRACE

To log an entire package (ex: everything for the JDBC multi-table origin, which happens to live in package com.streamsets.pipeline.stage.origin.jdbc.table), use a line like this:

log4j.logger.com.streamsets.pipeline.stage.origin.jdbc.table
log4j.logger.com.streamsets.pipeline.stage.origin.jdbc.table=TRACE