latest 6.2.x 6.1.x 6.0.x 5.8.x 5.7.x 5.6.x 5.5.x 5.4.x 5.3.x 5.2.x 5.1.x 5.0.x 4.18.x 4.17.0 4.16.x 4.15.x 4.14.x 4.13.0 4.11.x 4.8.0 4.7.0 4.6.0 4.5.0 4.4.0 4.2.0 4.1.0 4.0.0 3.22.0 3.21.0 3.20.0 3.19.0 3.18.0 3.17.0 3.16.0 3.15.0 3.14.0 3.13.0 3.12.0 3.11.0 3.10.0 3.9.0 3.8.0 3.7.0 3.6.0 3.5.0 3.4.0 3.3.0 3.2.0
Auto Light Dark
Auto Light Dark
latest 6.2.x 6.1.x 6.0.x 5.8.x 5.7.x 5.6.x 5.5.x 5.4.x 5.3.x 5.2.x 5.1.x 5.0.x 4.18.x 4.17.0 4.16.x 4.15.x 4.14.x 4.13.0 4.11.x 4.8.0 4.7.0 4.6.0 4.5.0 4.4.0 4.2.0 4.1.0 4.0.0 3.22.0 3.21.0 3.20.0 3.19.0 3.18.0 3.17.0 3.16.0 3.15.0 3.14.0 3.13.0 3.12.0 3.11.0 3.10.0 3.9.0 3.8.0 3.7.0 3.6.0 3.5.0 3.4.0 3.3.0 3.2.0

Enabling debug logging

Command to enable debug logging
curl -u admin -v -X PUT -d "" -H "Content-Type: application/json" http://localhost:7990/rest/api/latest/logs/logger/com.mohami/debug

  • Replace “admin” with the username for a Bitbucket administrator

  • Replace “localhost:7990” with the hostname and port of your Bitbucket instance.

  • If your Bitbucket instance is served via HTTPS, update the command above to “https://” instead of “http://”.

If the command is successful, you will see a log line like this in the Bitbucket logs:

[INFO] 2020-08-31 17:41:24,555 WARN  [hz.hazelcast.event-3]  com.mohami Switching to log level [debug]

Command to disable debug logging
curl -u admin -v -X PUT -d "" -H "Content-Type: application/json" http://localhost:7990/rest/api/latest/logs/logger/com.mohami/info

  • This command is identical to the first one, except with “info” instead of “debug” at the end.