You can use the logging feature in JIRA to monitor and
debug the Rational Adapter for JIRA. Logging can be configured to
specify profiles for logging and logging levels for individual features
and functions in JIRA.
About this task
By default, logging options for the Rational Adapter are
not visible. . To enable them, follow these steps:
Procedure
- Locate the log4j.properties file in your JIRA deployment.
A common location for it is jira-deployment/webapp/WEB-INF/classes/log4j.properties
- Locate the CLASS-SPECIFIC LOGGING LEVELS block and add
the following text to the list. This sets the logging level to INFO.
Note: Setting the logging level to DEBUG causes a large amount
of data to be included in the atlassian-jira.log file found in the
jira-home/logs folder.
# Start of OSLC Logging
log4j.logger.com.ibm.oslc.cm.adaptor.jira = INFO, console, filelog
log4j.additivity.com.ibm.oslc.cm.adaptor.jira = false
# End of OSLC Logging
- Stop and restart the JIRA server.
Results
After the JIRA server restarts, you can set the logging level
for the JIRA adapter by specifying the logging levels for com.ibm.oslc.cm.adaptor.jira.
By default, the logging levels are set to INFO.
What to do next
Review the available log files to monitor your system and
identify issues that might need to be addressed. You can view log
information from the Support section of the JIRA Administration page.
Go to
JIRA Administration > Systems > Troubleshooting >
Support