Purpose

The Bitbucket Server logs provide a lot of information, and in some cases, you may want to have specific events logged in a separate file for easy viewing or monitoring.

Solution

These sorts of modifications can be accomplished by editing <Bitbucket Server Installation>/atlassian-bitbucket/WEB-INF/classes/logback-spring.xml (or logback.xml if you are using a Bitbucket version prior to 7.0).

The example below will create a separate access log named atlassian-bitbucket-access-gitclone.log. 

The new log file will receive only git clone-related entries by checking only for events containing the string SSH - git-upload-pack.

• Create a new appender which is a copy of the bitbucket.accesslog appender.  Copy and add the lines below the bitbucket.accesslog appender:

              <appender name="bitbucket.accesslog" class="ch.qos.logback.core.rolling.RollingFileAppender">
                  <encoder>
                      <charset>UTF-8</charset>
                      <pattern>${accesslog.format}</pattern>
                  </encoder>
                  <file>${log.dir}/atlassian-bitbucket-access.log</file>
                  <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">
                      <fileNamePattern>${log.dir}/atlassian-bitbucket-access-%d.%i.log</fileNamePattern>
                      <maxFileSize>25MB</maxFileSize>
                      <maxHistory>10</maxHistory>
                  </rollingPolicy>
              </appender>
  
              <!-- This will create a separate access log for git clone operations. -->
              <appender name="bitbucket.accesslog.gitclone" class="ch.qos.logback.core.rolling.RollingFileAppender">
                  <filter class="ch.qos.logback.core.filter.EvaluatorFilter">      
                    <evaluator>
                      <expression>return ((String)mdc.get("a-request-action")).contains("SSH - git-upload-pack");</expression>
                    </evaluator>
                    <OnMismatch>DENY</OnMismatch>
                    <OnMatch>ACCEPT</OnMatch>
                  </filter>
                  <encoder>
                      <charset>UTF-8</charset>
                      <pattern>${accesslog.format}</pattern>
                  </encoder>
                  <file>${log.dir}/atlassian-bitbucket-access-gitclone.log</file>
                  <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">
                      <fileNamePattern>${log.dir}/atlassian-bitbucket-access-gitclone-%d.%i.log</fileNamePattern>
                      <maxFileSize>25MB</maxFileSize>
                      <maxHistory>10</maxHistory>
                  </rollingPolicy>
              </appender>

• Add a reference to the new appender named bitbucket.accesslog.gitclone inside the bitbucket.access-log logger

  Update the block of the bitbucket.access-log logger from this:

              <!-- Enable access logs and direct it to its own separate appender -->
              <logger name="bitbucket.access-log" level="INFO" additivity="false">
                  <appender-ref ref="bitbucket.accesslog"/>
              </logger>

  To this:

              <!-- Enable access logs and direct it to its own separate appender -->
              <logger name="bitbucket.access-log" level="INFO" additivity="false">
                  <appender-ref ref="bitbucket.accesslog"/>
                  <appender-ref ref="bitbucket.accesslog.gitclone"/>
              </logger>