Useful log files in Jira
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the server and data center platforms.
As an administrator of Jira Server / Data Center, it can be helpful to see a list of log files Jira creates and their locations, particularly for ingress into a log monitoring solution such as Splunk.
The following table lists the log files Jira creates and their default location and filename.
HTTP access log (tomcat)
A list of each request that Jira node receives and completes processing
Garbage collection log
Written by the JVM to describe how memory management takes place, and what memory is in use
Tomcat application server stdout
The stdout of the tomcat application server process
Primary Jira log file
Contains logging for most of Jira, including logs that aren’t specifically written elsewhere
Jira Software Agile Board log
Logging written by the Jira Software plugin
Jira Service Management log
Logging written by the Jira Service Management plugin
Records login success/failure transactions, session creation and destruction, along with certain authentication related debug logging if enabled
Apdex performance statistics
HTTP access log (Jira)
Secondary HTTP access log, written by Jira as opposed to Tomcat. Only written if HTTP access log debug is enabled
HTTP dump log (Jira)
HTTP dump log, written by Jira. A more verbose HTTP access log. Only written if HTTP dump logging is enabled
Incoming mail debug log. Only written to if Incoming Mail Debug is enabled.
Outgoing mail debug log. Only written to if Outgoing Mail Debug is enabled.
Writes performance statistics about the running Jira process
QueryDSL debug log
QueryDSL debug log, a SQL abstraction layer used by some Jira functions/plugins
Slow JQL log
Records JQL query and their source for executions over the threshold - by default 400ms
Slow QueryDSL log
Slow QueryDSL query log
SQL Debug Log
SQL debug and trace logging, if enabled
|atlassian-jira-app-monitoring.log*||Diagnostic Metrics||Logging written by Diagnostics plugin JMX logger (Jira 9+)|
|atlassian-jira-ipd-monitoring.log*||In-product-diagnostics DB||Logging written by Diagnostics plugin JMX logger for DB stats (Jira 9.3+)|
|JIRA_HOME/log/audit||YYYYmmdd.00000.audit.log||Audit logging||Filesystem historical logging of audit data|
|JIRA_HOME/log/jfr||atst_in_product_diagnostic_YYYY_MM_DD_HH_mm_ss.jfr||Java Flight Recorder||JFR data logging|
|atst_in_product_diagnostic_dump_on_exit_YYYY_MM_DD_HH_mm_ss.jfr||Java Flight Recorder||JFR data logging (auto-generated on exit)|
|active_configuration.jfc||Java Flight Recorder||Current JFR configuration|
|atst_in_product_diagnostic.settings||ATST||Settings for JFR functionalities|
The log files with a star "*" in the end indicate that the logs roll over. For example, the latest file is
atlassian-jira.log.2 and so on.
The number of log files is defined in the
log4j.properties file (if you're using Jira 9.4.x or older) or the
log4j2.xml file (if you're using Jira 9.5.x or newer). Both files are located in the Jira application installation directory.