Sometimes you may want more information about the processing of an email than you get from the Auditing report. Additional information can be configured to be logged out to a file. There are 2 methods for enabling logging:
| Table of Contents |
|---|
| maxLevel | 2 |
|---|
| exclude | Related Articles |
|---|
|
Output to a dedicated log file
Pre Jira 9.5.0 Log4j2 properties configuration
| Status |
|---|
| colour | Green |
|---|
| title | recommended |
|---|
|
| Status |
|---|
| colour | Blue |
|---|
| title | restart required |
|---|
|
With the following configuration, Jira will create a jemhsu.log file in JIRA_HOME/log. A Jira restart will be required to make the changes apply.
...
| Info |
|---|
Changing the amount of data loggedThe steps above set logging to the default level (DEBUG). This means that all extra information will be saved to the log file. To reduce the amount of logging, the level can be changed. Changing the level requires a Jira restart. The following levels can be set: |
| Note |
|---|
Using Jira 5?Jira 5 needs the first line to be: log4j.appender.JEMHFileLog=com.atlassian.jira.logging.MultiTenantJiraHomeAppender |
| Note |
|---|
Using Jira 9Jira 9 needs the ‘log4j.appender.JEMHFileLog.layout’ to be set as: log4j.appender.JEMHFileLog.layout=com.atlassian.logging.log4j.NewLineIndentingFilteringPatternLayout
|
Jira 9.5.0 and above Log4j2 XML configuration
...
| Status |
|---|
| colour | Blue |
|---|
| title | restart required |
|---|
|
...