Enabling debug logging

Should you have issues with Security for Confluence, turning on debug logging can help to troubleshoot and diagnose them.

Additional Logging Setting

Only Confluence administrators and users granted explicit app access can access these settings.

In the plugin configuration, you can enable additional logging under the Scanning Options heading by toggling the Enable additional logging switch.

This makes all Debug and Info level messages log as Warn messages on all nodes until the setting is turned off.

Interaction With Confluence Logging Configuration

Confluence allows more granular configuration of logging. Soteri recommends using the “Enable additional logging” setting to troubleshoot any issue with Security for Confluence. However, if for any reason you decide to use the Confluence logging configuration, it will not conflict with the Additional Logging Setting.

Enabling logging for database SQL commands

Logging all SQL commands will generate extremely verbose logs. It should only be enabled temporarily, at the instruction of our support team.

1. Go to  ⚙️ → General Configuration → Logging and Profiling.

2. Under Add New Entry enter org.hibernate.SQL at DEBUG level and click Add entry

3. Under Add New Entry enter net.java.ao at DEBUG level and click Add entry

4. Under Add New Entry enter com.querydsl.sql at DEBUG level and click Add entry

Reference: https://confluence.atlassian.com/doc/enabling-detailed-sql-logging-179030.html