Where is atlassian jira.log

Once these settings are changed, reproduce the issue on your JIRA instance, so that traces are logged. For Server: Click on the create zip button and download the logs as shown in the below screenshot:. For Datacenter: Click on the create zip button for all the nodes and download the logs as shown in the below screenshot:. Alternatively, you can opt for the below option:. Go to the directory where you have installed JIRA on your server. In case you do not find the files, trigger the below commands in the UNIX terminal which would fetch the list of logs files path.

Only written if HTTP access log debug is enabled. HTTP dump log, written by Jira. A more verbose HTTP access log. Only written if HTTP dump logging is enabled. Atlassian Support Jira Software 8. Related content No related content found. Still need help? The Atlassian Community is here for you. Only written if HTTP access log debug is enabled atlassian-jira-http-dump.

For all of the following procedures, you must be logged in as a user with the Jira System Administrators global permission. In the log4j. Note: If you change the location of your log files, they will no longer be included when you generate a support zip.

This means you'll need to attach your logs to any support requests manually. Each logging level provides more logging information that the level before it:. The default level is WARN, meaning warnings and errors are displayed. Sometimes it is useful to adjust this level to see more detail. If you are unsure of which logging categories to adjust, the most helpful information generally comes from the log4j.

The log4j. For more information about log4j e. Please note: If your application server configures logging itself, you may need to remove the log4j.