#APACHE TOMCAT LOGS LOCATION HOW TO#
#APACHE TOMCAT LOGS LOCATION INSTALL#
#APACHE TOMCAT LOGS LOCATION FULL#

#APACHE TOMCAT LOGS LOCATION INSTALL#

There are some additional logs in your Confluence install directory that can be useful when troubleshooting issues with your Confluence site. Is a sample error : Unable to find sample error

#APACHE TOMCAT LOGS LOCATION HOW TO#

See Troubleshooting Problems and Requesting Technical Support to find out how to set up a periodic scan of your log files. Scanning log files for known problemsĪtlassian Troubleshooting and support tools includes a log analyzer that can check for you Confluence logs for errors and match them against known problems in our knowledge base and issue tracker. See How to Enable User Access Logging in our Knowledge Base. You can however configure the application log to show which users are accessing which pages in Confluence. These logs are not part of the application log, and can be found at /logs/conf_access_log.log. Log the details of users accessing each Confluence pageĪccess logging using Tomcat Valve is enabled by default from Confluence 7.11. This is useful for troubleshooting specific problems. You may want to increase Confluence's logging so that it records individual SQL requests sent to the database. Log the details of SQL requests made to the database Here's some specific log configurations you may need when troubleshooting. See Configuring Logging for instructions on how to change the logging configuration of Confluence. You can change the default log size and the number of log files to keep by editing the following values in /confluence/WEB-INF/classes/log4j.properties file. Change the size and number of log filesīy default, Confluence keeps 5 application log files, which are overwritten as they reach 20 MB. This means you'll need to attach your logs to any support requests manually.

Note: If you change the location of your log files, they will no longer be included when you generate a support zip. Read more about appenders in the log4j documentation.įor more detailed information see Configuring log4j in Confluence to send specific entries to a different log file in our Knowledge Base.

#APACHE TOMCAT LOGS LOCATION FULL#

The Synchrony log destination can also be changed in the same way in file.Ĭonfluence ships with the full suite of appenders offered by log4j. Comment out the previous lines referring to the ConfluenceHomeLogAppender. – If you want to log to a different location, uncomment the RollingFileAppender line and change the destination file in the line below it.This appender allows the following settings: .ConfluenceHomeLogAppender – This is a custom appender which controls the default logging destination.In the standard properties file, you will find entries for two appenders: 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. In log4j, an output destination is called an 'appender'. This file is a standard log4j configuration file, as described in the Apache log4j documentation. confluence/WEB-INF/classes/log4j.properties The logging behavior for Confluence and Synchrony is defined in the following properties file: You can check the exact classes or packages that are logged to each file in the log4j.properties file under LOGGING LOCATION AND APPENDER. In our documentation, when we refer to the 'application log', we are referring to any of these files. This file contains details about issues and errors detected during the startup of your Confluence instance that need to be resolved. This file contains entries related to migration to Cloud. This file contains entries for in-product diagnostics including database connectivity and HTTP connection metrics which helps with identifying performance issues in your infrastructure. atlassian-confluence-ipd-monitoring.log.This file contains entries for Java Management Extensions API metrics which allow you to monitor the status of your instance in real time. This file contains entries for an experimental diagnostics feature which provides alerts for things like low disk space and memory. This file contains entries related to Synchrony, which powers collaborative editing. This file contains entries related to your users and user directories. This file contains entries related to outgoing mail, such as notifications. This file contains entries related to the search index. When you start Confluence, any log entries written to the console will also be repeated in this log. This is the main application log file, most entries will be written here. To make troubleshooting problems easier, the application log is split into several distinct log files: This location is configurable, so you may need to check the log config for your location. By default, the application log files can be found in the /logs directory.

Apache tomcat logs location