Issue Summary

Helm charts will mount accessLog location pointing to a subPath of localHomeSubPath pointing to "log" and that will mix up Tomcat and Application logs in the same place.

The consequence is that Support zips will carry on duplicate data across different folders, which will take significantly more time to finalise and will produce larger datasets without proper reason.

It also adds more trouble to Support as it is necessary to trim such files from the troubleshooting, especially if they are large.

This is reproducible on Data Center:

Steps to Reproduce

1. In https://github.com/atlassian/data-center-helm-charts check values.yaml
2. Find accessLog
3. Match the value of localHomeSubPath with the application's default log folder in localHome. In case they match, for example, in Confluence </opt/atlassian/confluence/logs and /var/atlassian/application-data/logs are a match, and both log types will end up stored on the same backend volume.

Other applications may follow.

Expected Results

Application logs and Tomcat logs should be separated. That will allow Support zips to collect the required files and avoid duplication in the bundled files.

Actual Results

As both folders will contain the same data, Support zips will carry on unnecessarily duplicated files which will be stored in separate folders within the Zip file and slow down any troubleshooting.

Workaround

In values.yaml modify localHomeSubPath to a distinct location, for example tomcat-logs