topic Re: Activiti log for debug in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/activiti-log-for-debug/m-p/222799#M175929 <HTML><HEAD></HEAD><BODY><SPAN>Sure, just set the relevant classes in your log4j config, </SPAN><BR /><BR /><SPAN>like </SPAN><BR /><BR /><SPAN>log4j.logger.org.activiti.engine.whatever=DEBUG</SPAN><BR /><SPAN>log4j.logger.org.activiti.engine.somethingelse=INFO</SPAN></BODY></HTML> Mon, 07 Mar 2016 10:31:55 GMT jbarrez 2016-03-07T10:31:55Z Activiti log for debug https://connect.hyland.com/t5/alfresco-archive/activiti-log-for-debug/m-p/222798#M175928 Hi,We found that activiti log at INFO level provides little info to know was going on but at DEBUG level to much info, many not relevant. We want configure log4j to target specific classes or package to DEBUG level to provide antiquate info to know what is going on. Has anyone tried this approach an Fri, 04 Mar 2016 14:09:49 GMT https://connect.hyland.com/t5/alfresco-archive/activiti-log-for-debug/m-p/222798#M175928 aimingxu 2016-03-04T14:09:49Z Re: Activiti log for debug https://connect.hyland.com/t5/alfresco-archive/activiti-log-for-debug/m-p/222799#M175929 <HTML><HEAD></HEAD><BODY><SPAN>Sure, just set the relevant classes in your log4j config, </SPAN><BR /><BR /><SPAN>like </SPAN><BR /><BR /><SPAN>log4j.logger.org.activiti.engine.whatever=DEBUG</SPAN><BR /><SPAN>log4j.logger.org.activiti.engine.somethingelse=INFO</SPAN></BODY></HTML> Mon, 07 Mar 2016 10:31:55 GMT https://connect.hyland.com/t5/alfresco-archive/activiti-log-for-debug/m-p/222799#M175929 jbarrez 2016-03-07T10:31:55Z