Logging to atlassian-bitbucket.log from a Bitbucket plugin

[JohnLawlor]

I am trying to debug a plugin which doesn’t work in 8.0. I am wondering how to write log messages to atlassian-bitbucket.log from the plugin. I tried the logback option discussed here:

Logging in a plugin for Bitbucket server?

To enable debugging of your Bitbucket plugin using Logback: Create the directory src/test/resources/bitbucket-home Create a file src/test/resources/bitbucket-home/logback.xml [1] and add logger elements as desired, eg I have: <included> <appender name="console" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>${log.format}</pattern> </encoder> </appender> <!--When starting up Elasticsearch in-process (for dev): We need to set the log…

It didn’t make any difference however. I also tried to write logs to a different file altogether using this configuration:

<included>
    <appender name="filehook-plugin" class="ch.qos.logback.core.RollingFileAppender">
        <encoder>
            <pattern>${log.format}</pattern>
        </encoder>
    </appender>
    <logger name="org.christiangalsterer.stash.filehooks.plugin.hook" level="INFO"/>
    <file>${log.dir}/filehooks-plugin.log</file>
</included>

That also didn’t work.

[UlrichKuhnhardtIzym1]

I can recommend a solution that changes the log level of any package at runtime. Send a PUT request to BB REST API like so:

curl -u admin:admin -v -ikL -X PUT -d ""  -H "Content-Type: application/json" "http://localhost:7990/bitbucket/rest/api/latest/logs/logger/org.christiangalsterer.stash.filehooks.plugin.hook/debug"

To reset the package log level to INFO or WARN end the URL with .../info or .../warn or restart bitbucket.

Hope that helps.
Cheers Ulrich
// Izymes

[JohnLawlor]

What worked for me was simply enabling Debug in the web UI:

With that change in place and using logback, messages logged at INFO level appeared in the atlassian-bitbucket.log file. I didn’t actually need the custom xml file at all.