Sometimes it is interesting to enable debug logging to better understand behaviour that is not as expected. It differs across the Atlassian products how this is done. If you cannot find relevant documentation for your product below, please contact us and we will help you out. For the other products than Jira and Confluence, you will have to enable logging by editing log configuration files and restart your instance.

Jira

Go to the URL <your-jira-url>/secure/admin/ViewLogging.jspa

On this page press the link: Configure logging level for another package.

Then add the following logging (se image below).

Package name: org.kantega.atlaskerb

Logging level: DEBUG

Then you can perform the activity you experience to not work as expected. The DEBUG logging will stay on until next restart of Jira or until you turn it off again manually on the page.

If you need additional help understanding the logs, please post us a support query and attach log file.

Confluence

Go to the page Logging and Profiling <your-confluence-url>/admin/viewlog4j.action

Then input in Class/Package Name value: org.kantega.atlaskerb

For New Level select: DEBUG


Press Add entry

Then you can perform the activity you experience to not work as expected. The DEBUG logging will stay on until next restart of Jira or until you turn it off again manually on the page.

If you need additional help understanding the logs, please post us a support query and attach log file.