For Jira and Confluence

The logging level can be increased for troubleshooting. To do this, go to the Jira/Confluence Logging and Profiling (in the Administration section) configuration and add the following new entry: 

de.resolution with DEBUG level

If you are using the User Sync SCIM Connector, you can use the following package: de.resolution.usersync.builtin.scim

After that, the plugin starts detailed logging in the

<JIRA home directory>/log/atlassian-jira.log  

<Confluence home directory>/log/atlassian-confluence.log

For Bitbucket

To increase the plugin logging level for troubleshooting in Bitbucket, please follow the steps below:

1. Mark the checkbox Enable debug logging in the Bitbucket Logging and Profiling configurations:
   
   
2. You can choose now between adding the plugin debug logging packages on startup or at runtime:
   1. On startup

      1. To enable plugin debug logging whenever Bitbucket Server is started, edit the <Bitbucket home directory>/shared/bitbucket.properties file (if this file doesn't exist then you should create it) and add the following line:

         logging.logger.de.resolution=DEBUG
         
         or
         
         logging.logger.de.resolution.usersync.builtin.scim=DEBUG

         CODE
   2. At runtime
      

      1. To enable debug logging once Bitbucket Server has been started, edit the <ADMIN_USERNAME> and  <BASE_URL> part with your information and run the following command in your terminal:

         curl -u admin -v -X PUT -d "" -H "Content-Type: application/json" https://<BASE_URL>/rest/api/latest/logs/logger/de.resolution/debug

         CODE

         After that, the plugin starts detailed logging in the <Bitbucket home directory>/log/atlassian-bitbucket.log.

3. Restore default logging after enabling debug logging
   
   1. Please uncheck the checkbox Enable debug logging in the Bitbucket Logging and Profiling configurations and Save your settings.

1. 1. On startup
      
      1. edit the <Bitbucket home directory>/shared/bitbucket.properties file and remove the following line:

logging.logger.de.resolution=DEBUG

or

logging.logger.de.resolution.usersync.builtin.scim=DEBUG

1. 1. At runtime
      1. To disable debug logging for the de.resolution logger, run this command in a terminal:

curl -u admin -v -X PUT -d "" -H "Content-Type: application/json" https://<BASE_URL>/rest/api/latest/logs/logger/de.resolution/warn

Log the start and end of a sync

After enabling INFO level logging for de.resolution.usersync.startstop, messages like this are written to the log for every sync on start and end:

2023-08-03 07:54:50,751+0000 Caesium-1-1 INFO ServiceRunner     [d.resolution.usersync.startstop] Starting sync for Connector new Testconnector (11045589-5b61-443b-8bca-e1d7619d756e)
2023-08-03 07:54:52,149+0000 Caesium-1-1 INFO ServiceRunner     [d.resolution.usersync.startstop] Ended sync for Connector new Testconnector (11045589-5b61-443b-8bca-e1d7619d756e), status is DONE with result SUCCESS, check Sync Status 86 for details.

In our KB article How to monitor User Sync for Failures you will find more details and examples.