Hi
I have a use case in which i want to log bad records in the log file. I have configured the log4j property file is getting generated as well but it also going to flink logs as well i want to detach it from flink logs want to write to log file. .Here is configuration (Note :AMSSource is the custom written adaptor here) # This affects logging for both user code and Flink log4j.rootLogger=INFO, file log4j.logger.amssource=DEBUG, amssourceAppender # Uncomment this if you want to _only_ change Flink's logging #log4j.logger.org.apache. # The following lines keep the log level of common libraries/connectors on # log level INFO. The root logger does not override this. You have to manually # change the log levels here. log4j.logger.akka=INFO log4j.logger.org.apache.kafka= log4j.logger.org.apache. log4j.logger.org.apache. # Log all infos in the given file log4j.appender.file=org. log4j.appender.file.file=D:\\ log4j.appender.file.append= log4j.appender.file.layout= log4j.appender.file.layout. # Suppress the irrelevant (wrong) warnings from the Netty channel handler log4j.logger.org.apache.flink. #BonusPointAppender log4j.appender. log4j.appender. log4j.appender. log4j.appender. log4j.appender. #log4j.appender. log4j.appender. log4j.appender. #AMSSourceAppender log4j.appender. log4j.appender. log4j.appender. log4j.appender. log4j.appender. #log4j.appender. log4j.appender. log4j.appender. |
Hi, TBH, I don't have much experience with logging, but you might want to consider using Side Outputs [1] to route invalid records into a separate stream.2018-03-20 10:36 GMT+01:00 Puneet Kinra <[hidden email]>:
|
Hi Fabin thanks for reply I fixed the issue that i was facing. On Tue, Mar 20, 2018 at 7:31 PM, Fabian Hueske <[hidden email]> wrote:
|
Free forum by Nabble | Edit this page |