Change logging levels in Jira Server
プラットフォームについて: Server と Data Center のみ - この記事は、サーバーおよびデータセンター プラットフォームのアトラシアン製品にのみ適用されます。
The purpose of this article is to show how you can set the logging level for a package in JIRA.
Setting the logging level temporarily
There are options within JIRA to temporarily configure the logging level for a package using the Logging and Profiling page:
- To increase/decrease the logging level for a package already listed, choose the level on the right hand side in the 'Set Logging Level' column.
- To set the logging level for another package, that isn't listed, choose the option to Configure logging level for another package. That will prompt you to specify the package and logging level.
Setting the logging level permanently
The information in this page relates to customisations in JIRA. Consequently, Atlassian Support cannot guarantee to provide any support for the steps described on this page as customisations are not covered under Atlassian Support Offerings. Please be aware that this material is provided for your information only and that you use it at your own risk.
Also, please be aware that customisations done by directly modifying files are not included in the upgrade process. These modifications will need to be reapplied manually on the upgraded instance.
If you are looking to set the logging level for a package permanently, you can do so by configuring the
log4j.properties file, located in the
Example of setting the logging level for a package in log4j.properties.
- Look at the logging level for the package com.atlassian.jira.issue.index we can see it is set to INFO level logging:
log4j.logger.com.atlassian.jira.issue.index = INFO, console, filelog
- To persistently set this to DEBUG level logging, you'll want to update the logger config for that package. In this example we have commented out the INFO level logger, and added a DEBUG level logger for the com.atlassian.jira.issue.index package:
#log4j.logger.com.atlassian.jira.issue.index = INFO, console, filelog log4j.logger.com.atlassian.jira.issue.index = DEBUG, console, filelog
Restarting JIRA is necessary to pick up any changes to log4j.properties