Issue Summary

It has been observed that atlassian-bitbucket-ipd-monitoring.log and atlassian-bitbucket-perf.log are not rotating and keep on increasing within the same file.

To troubleshoot the issue, we have verified the logback-spring.xml file for both the IPD and Perf logs sections and found below observation while comparing the patterns with other log files like access log, mail log, alert log etc. in the same file:

Steps to Reproduce

1. Launch a new Bitbucket 9.4.8 version.
2. Enable IPD monitorting in Bitbucket (UI -> Administration -> select System, and go to Troubleshooting and support tools -> Diagnostic settings -> Enable both options -> Runtime and Thread Diagnostic)
3. Now go to <Bitbucket_Install_Path>/app/WEB-INF/classes/logback-spring.xml file on Bitbucket Server/ Nodes.
4. Change the file sizes from 25MB to 25KB (if you want to replicate the issue sooner)
5. Try increasing the existing file size beyond 25KB by adding more rows.
6. File size will keep on increasing, but a new rotation file will not get created for both ipd and perf logs under <Bitbucket_Home>/log folder. 

Expected Results

1. File size should get rotated beyond 25MB or size defined like other logs (access log, alerts log, mail log etc.)

Actual Results

The same file generated initially keeps growing instead of rotating after the file size increases.

Workaround

After replacing the entries for ipd and perf logs (from atlassian-bitbucket-ipd-monitoring.log.%i to ${log.dir}/atlassian-bitbucket-ipd-monitoring.log.%i) in the logback-spring.xml file, files should start rotating.

Current entry for ipd and perf logs separately:

<fileNamePattern>atlassian-bitbucket-access-%d.%i.log</fileNamePattern>

Replace it with:

<fileNamePattern>${log.dir}/atlassian-bitbucket-access-%d.%i.log</fileNamePattern>

Note: After applying the above changes, a restart of Bitbucket is required.