Our JBOSS console logs are being flooded by Kafka INFO log records. We’ve reviewed the advanced config documentation for the stream service but can’t see any option to adjust Kafka log levels.
We thought about modifying the log4j.properties file under the pegatemp/kafka/config directory but this would get deleted should we remove pega temp at any time.
We also note that Kafka classes are outside the scope of the System>Operations>Logging Level Settings.
Any suggestions? Thanks
have you tried the setting: dsm/services/stream/pyBaseLogPath (in the article you quoted)? This will allow kafka distribution not being deleted when you delete the temp dir (that was the default).
We’ve changed the values in log4j.properties file in /apps/pegatemp/kafka-1.1.0.4/config to WARN rather than INFO but we’re still seeing the same level of excessive messaging in console.log and server.log. Our app server exhausted it’s file space last night because of it. Is there another config file where Kafka logging needs to be adjusted? We’ve also updated connect-log4j.properties.
I have added these two setting on my “standalone.xml” to prevent kafka client’s (consumer or producer) INFO level logging.
…
...pega-tmpdir/kafka-1.1.x.x/config files are for kafka server. such as zookeeper, broker.
I am not sure, any other good solution might exist.
Thanks! That worked.