Working with Confluence Logs
Confluence 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.
If you request help from Atlassian Support, we will almost always ask for the
atlassian-confluence.log from the
confluence-home/logs directory. You can access the logs from the Confluence Administration Console, via the support tool. If you cannot access the Confluence Administration Console, check the properties file at
<confluence-installation>/confluence/WEB-INF/classes/confluence-init.properties, look for the
confluence.home setting in that file, then find the logs in the Confluence home directory.
Finding the Confluence Log Files
This 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
atlassian-confluence.log as its primary log, not the application server log.
Both the Confluence and Confluence EAR/WAR distributions follow the same default behaviour:
- When you start Confluence, log entries will be sent to the application server logs until Confluence has completed its initial bootstrap. Any log entries written to the console will be repeated into the log in the Confluence home directory as described below.
- Once the initial startup sequence is complete, all logging will be to
<confluence-home>/logs/atlassian-confluence.log. For example:
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 File
Confluence'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 Files
Terminology: 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, you will find entries for two appenders:
com.atlassian.confluence.logging.ConfluenceHomeLogAppender– This is a custom appender which controls the default logging destination described above. This appender allows the following settings:
org.apache.log4j.RollingFileAppender– If you want to log to a different location, uncomment the
RollingFileAppenderline and change the destination file in the line below it. Comment out the previous lines referring to the
Confluence ships with the full suite of appenders offered by log4j. Read more about appenders in the log4j documentation.
Changing the Logging Levels
See Configuring Logging for instructions on how to change the logging configuration of Confluence.
Using Some Specific Confluence Logging Options
This section contains some pointers to specific log configurations you may need.
Log the Details of SQL Requests made to the Database
You 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:
- At runtime – see instructions above.
- Via the logging properties file – see the detailed instructions.
Log the Details of Users Viewing/Accessing each Confluence Page
You 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 Problems
Confluence 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.
- Finding the thread dumps. Thread dumps are logged to the application server log file.
Was this helpful?
Thanks for your feedback!