Enabling additional logging in Fisheye/Crucible
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Depending on the issue, it may be required to increase the log level in Fisheye/Crucible for a particular set of classes.
If you have been asked to turn on Debug Logging, you can enable this by going to the Fisheye Admin Page > Global Settings > Server > Debug Logging. General Debug Logging does not require a restart and is usually a good place to start. This page contains the list of the available loggers and their usage that augment the general Debug Logging.
Solution
SQL logging
This may be required when some pages/actions are slow to load and more details about the queries are required.
Procedure
Add the following block of code to your
<FishEye install directory>/log4j.xmlfile:
1
2
3
4
5
6
7
<logger name="org.hibernate.type">
<level value="trace"/>
</logger>
<logger name="org.hibernate.SQL">
<level value="DEBUG"/>
</logger>Restart Fisheye/Crucible
On this page
Was this helpful?