Geoffrey De Smet created JBRULES-3551: ----------------------------------------- Summary: KnowledgeRuntimeLogger should be activable by enabling category logging and send it's output to slf4j Key: JBRULES-3551 URL: https://issues.jboss.org/browse/JBRULES-3551 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core (expert) Environment: http://docs.jboss.org/drools/release/5.4.0.Final/drools-expert-docs/html_... Reporter: Geoffrey De Smet Assignee: Mark Proctor Drools's audit logging should log to slf4j, so the user can easily configure advanced logging features such as rolling files, zipped files, ... Also enabling the logging should be user friendly. So instead of this: {code} KnowledgeRuntimeLogger logger = KnowledgeRuntimeLoggerFactory.newFileLogger(ksession, "logdir/mylogfile"); ... logger.close(); {code} They just enable it in the logger configuration (logback.xml or log4j.xml): {code} <logger name="org.drools.logger.audit" level="trace"/> {code} This way, drools's audit logging is no longer the odd duck in the normal logging output. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira