I was able to "Enable Page Profiling" on our dev server and see the additional output in the atlassian-confluence.log right away.
However on the prod server when I "Enable Page Profiling" nothing additional is being written. Any ideas? Could this be because the log4j.properties file has been changed by someone else to override admin UI settings ? And if so how can I re-enable logging control from the Confluence Admin UI "Logging and Profiling" page?
My suggestion would be to diff the production log4j.properties and the dev log4j.properties files and see if there are changes.
One thing I've found is that when enabling Diagnostic logging from the admin menus (clicking on that handy button that changes all the appropriate classes to DEBUG level) the atlassian-confluence.log is closed and the DEBUG level logging happens in the catalina.out. Pretty straight forward.
Now go do your whatever you need to test and then return to the logging page to disable the diagnostic logging level by clicking the production logging button (everything is returned to it's original value as per the log4j.properties file). Regular logging ensues.
GOTCHA here is that logging to atlassian-confluence.log does not continue until you restart Confluence. So if someone previously enabled diagnostic level but you haven't restarted yet, you may not be seeing any logging to the atlassian-confluence.log.
Hope that helps.
Most of us don’t need much convincing that stakeholder management is important. It just makes sense that keeping everyone in-the-know on projects and assigning clearly defined roles is key to having ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs