Confluence 4.0 : Working with Confluence Logs
This page last changed on Feb 23, 2011 by smaddox.
Finding the Confluence Log FilesThis section describes Confluence's default logging behaviour, assuming that you have not changed the destination of the logs. In order to unify logging across different application servers, Confluence uses the Both Confluence Standalone and EAR/WAR distributions follow the same default behaviour:
Note that the default location is the Confluence home directory, not the application server's log file. The home directory is specified in
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 In the standard properties file, 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. Scanning Log Files for Known ProblemsConfluence provides an inbuilt log scanner that will check your Confluence logs for errors and attempt to match them against known issues in our knowledge base and bug tracker. See Troubleshooting Problems and Requesting Technical Support#scanner. Notes
RELATED TOPICSImportant Directories and Files |
![]() |
Document generated by Confluence on Sep 19, 2011 02:42 |