Confluence Docs 3.0 : Working with Confluence Logs
This page last changed on Sep 25, 2009 by jlargman.
On this page: Logs LocationThis section describes Confluence's default logging behaviour, assuming that you have not changed the destination of the logs. So as to unify logging across different application servers, Confluence uses the atlassian-confluence.log, not the application server log, as it's primary log.
For Confluence 2.6.x and earlier, the default behaviour is:
For Confluence 2.7.x and later, both Standalone and EAR/WAR distributions follow the same default behaviour:
BackgroundConfluence uses Apache's log4j logging service. This allows a developer or administrator to control the logging behavior and the log output file by editing a configuration file, without touching the application binary. There are six known log4j logging levels. Finding the Log Configuration FileConfluence's logging behaviour is defined in the following properties file: This file is a standard log4j configuration file, as described in the Apache log4j documentation. Changing the Destination of the Log FilesTerminology: In log4j, an output destination is called an 'appender'. To change the destination of the log files, you need to stop Confluence and then change the settings in the 'Logging Location and Appender' section of the log4j.properties file. The location of this file is described above. In the standard properties file supplied with Confluence 2.7 and later, you will find entries for two appenders:
Confluence ships with the full suite of appenders offered by log4j. Read more about appenders in the log4j documentation. Changing the Logging LevelsSee Configuring Logging for instructions on how to change the logging configuration of Confluence. Using Some Specific Confluence Logging OptionsThis section contains some pointers to specific log configurations you may need. Log the Details of SQL Requests made to the DatabaseYou may want to increase Confluence's logging so that it records individual SQL requests sent to the database. This is useful for troubleshooting specific problems. You can enable detailed SQL logging in two ways:
Log the Details of Users Viewing/Accessing each Confluence PageYou can configure the log to show which users are accessing which pages in Confluence. This can only be done via the logging properties file – see the detailed instructions. Where are my Thread Dumps?Thread dumps are logged to the application server log file. RELATED TOPICS
|
![]() |
Document generated by Confluence on Nov 05, 2009 23:27 |