...
| Note |
|---|
Please be aware that with the log level set to DEBUG or TRACE, some of the data written to the log file may be considered private or confidential (e.g. email addresses or even email contents). |
In Jira
Set Log Level
Go to JIRA Administration > System
On the left, select Logging and profiling
Scroll down to Default loggers and click on Configure logging level for another package
As package name, enter net.savignano
...
and select logging level DEBUG
On Linux, the log files will usually be here (but your installation may use a different location):
...
On production instances, preferably set a mark by entering a unique string into the Message field.
In Confluence
Go to Confluence Administration > General Configuration
On the left, scroll down to Logging and Profiling
At Add New Entry, set to Debug and enter net.savignano
...
as package name
On Linux, the log files will usually be here (but your installation may use a different location):
...
Once you have that app installed, it’s as simple as this:
On the Bitbucket Administration page, click Advanced Logging
At Add New Entry, enter net.savignano
...
and select logging level DEBUG
Note that this will be unset when Bitbucket is restarted.
...
If you do not have that app and cannot or do not want to install it, the log level can only be adjusted by modifying the logging configuration file. On Linux, it is usually located at /opt/atlassian/bitbucket/app/WEB-INF/classes/logback-spring.xml (or logback.xml before Bitbucket 7.0).
Open the file in an editor, and after the last existing
<logger .. />entry, add the following lines:
| Code Block | ||
|---|---|---|
| ||
<!-- S/Notify logging -->
<logger name="net.savignano.snotify" level="DEBUG"/> |
2. To activate the configuration, it is required to restart Bitbucket.
...