Description
Most times, problems can be resolved by discussion of the symptoms and/or having recreation steps that can be reproduced. In some cases, this may not be sufficient and may require some additional data collection. This can be done relatively easily with support available in JIRA, Confluence, and Bamboo for adding temporary logging levels without requiring a server restart. See the links below for more details. This involves turning on DEBUG logging for specific packages.
For most plugins provided by Bob Swift Software, the easiest (most general package) thing to use is org.swift. This should be fine for 99% of the cases. More specific packages may be needed to reduce the amount of logging if more than one plugin has been installed and there is heavy use.
Newer add-ons may use the com.appfire prefix - for example Code Pro for Confluence and SQL for Bamboo.
Add DEBUG logging at runtime
- Go to Administration -> Logging and Profiling
- Find the Add new entry area near the top of the page
- Add the following entry for the Class/Package Names: org.swift
- Select DEBUG for the New Level value and click Add entry
- Log statements will appear in the standard Confluence log file.
- Go to the server and find the application server log file or create a Support Zip using the Atlassian Tools.
- Attach the relevant sections from the application server log, the entire log file, or ZIP to the Jira issue you have created.
Logging will occur immediately, but only last until Confluence is restarted.
You will want to be sure and go back and remove the entry that was added after you have completed triaging your issue.
No direct access to server log?
References
- Confluence logging and profiling - How to configure additional temporary logging in Confluence
- JIRA logging and profiling - How to configure additional temporary logging in JIRA
- Bamboo logging - How to configure additional temporary logging in Bamboo
