• 1
    • 5
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      Right now most of the Bamboo log is present in the catalina.out since it seems to log the whole content from atlassian-bamboo.log plus the Tomcat logs. The atlassian-bamboo.log also logs the content from the access_log.<date> but in this case a bit trimmed. In other words, we have multiple files with repeated information consuming space and also cluttering the specific log content.

      Suggested Solution

      • The catalina.out should hold Tomcat specific logs (the default log4j configuration should be adjusted for this)
      • The atlassian-bamboo.log should hold only the product log (without the access logs, since they are present in a different file)

      Workaround for catalina.out logging

      The Log4j.properties can be configured to show only the relevant bamboo information in catalina.out

              cglockner Christian Glockner
              dsantos Daniel Santos (Inactive)
              Votes:
              12 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: