Uploaded image for project: 'Server Deployments and Scale'
  1. Server Deployments and Scale
  2. SCALE-78

Enable Tomcat Access Logging in Confluence AWS Quickstart

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • AWS Quick Start
    • None

    • 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

      When a Confluence cluster is started using the AWS Quickstart Template, the server.xml is created based on the template below:

      The Tomcat Access Logging is not included in the template despite it has been enabled by default since Confluence 7.11.

      Ref:

      Suggestion

      Enable the AccessLogValve by default for Confluence as it is important for Support during troubleshooting

            [SCALE-78] Enable Tomcat Access Logging in Confluence AWS Quickstart

            Vadym Kovalskiy (Inactive) added a comment -

            Created task - https://bulldog.internal.atlassian.com/browse/CLIP-1652

            Vadym Kovalskiy (Inactive) added a comment - Created task - https://bulldog.internal.atlassian.com/browse/CLIP-1652
            Vadym Kovalskiy (Inactive) made changes -
            Remote Link New: This issue links to "CLIP-1652 (Bulldog)" [ 680913 ]
            Damien Tan made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 677144 ]
            Damien Tan made changes -
            Description Original: h3. Problem
            When a Confluence cluster is started using the AWS Quickstart Template, the {{*server.xml*}} is created based on the template below:
            * https://bitbucket.org/atlassian/dc-deployments-automation/src/master/roles/confluence_config/templates/server.xml.j2

            The [Tomcat Access Logging|https://confluence.atlassian.com/confkb/audit-confluence-using-the-tomcat-valve-component-223216846.html] is not included in the template despite it has been enabled by default since Confluence 7.11.

            Ref:
            * Jira AWS Quick start on the other hand [already has it enabled|https://bitbucket.org/atlassian/dc-deployments-automation/src/4854676d50f248d8081c94f437db727f90dba839/roles/jira_config/templates/server.xml.j2#lines-84]
            * Confluence Docker also [have an option to enable|https://hub.docker.com/r/atlassian/confluence-server/] it

            h3. Suggestion
            Enable the {{AccessLogValve}} by default for Confluence as it is important for Support during troubleshooting             		New: h3. Problem
            When a Confluence cluster is started using the AWS Quickstart Template, the {{*server.xml*}} is created based on the template below:
            * https://bitbucket.org/atlassian/dc-deployments-automation/src/master/roles/confluence_config/templates/server.xml.j2

            The [Tomcat Access Logging|https://confluence.atlassian.com/confkb/audit-confluence-using-the-tomcat-valve-component-223216846.html] is not included in the template despite it has been enabled by default since Confluence 7.11.

            Ref:
            * Jira AWS Quick start on the other hand [already has it enabled|https://bitbucket.org/atlassian/dc-deployments-automation/src/4854676d50f248d8081c94f437db727f90dba839/roles/jira_config/templates/server.xml.j2#lines-84]
            * Confluence Docker image also [have an option to enable|https://hub.docker.com/r/atlassian/confluence-server/] it

            h3. Suggestion
            Enable the {{AccessLogValve}} by default for Confluence as it is important for Support during troubleshooting
            Damien Tan made changes -
            Description Original: h3. Problem
            When a Confluence cluster is started using the AWS Quickstart Template, the {{*server.xml*}} is created based on the template below:
            * https://bitbucket.org/atlassian/dc-deployments-automation/src/master/roles/confluence_config/templates/server.xml.j2

            The [Tomcat Access Logging|https://confluence.atlassian.com/confkb/audit-confluence-using-the-tomcat-valve-component-223216846.html] is not included in the template despite it has been enabled by default since Confluence 7.11.

            Ref: Jira on the other hand [already has it enabled|https://bitbucket.org/atlassian/dc-deployments-automation/src/4854676d50f248d8081c94f437db727f90dba839/roles/jira_config/templates/server.xml.j2#lines-84]

            h3. Suggestion
            Enable the {{AccessLogValve}} by default for Confluence as it is important for Support during troubleshooting             		New: h3. Problem
            When a Confluence cluster is started using the AWS Quickstart Template, the {{*server.xml*}} is created based on the template below:
            * https://bitbucket.org/atlassian/dc-deployments-automation/src/master/roles/confluence_config/templates/server.xml.j2

            The [Tomcat Access Logging|https://confluence.atlassian.com/confkb/audit-confluence-using-the-tomcat-valve-component-223216846.html] is not included in the template despite it has been enabled by default since Confluence 7.11.

            Ref:
            * Jira AWS Quick start on the other hand [already has it enabled|https://bitbucket.org/atlassian/dc-deployments-automation/src/4854676d50f248d8081c94f437db727f90dba839/roles/jira_config/templates/server.xml.j2#lines-84]
            * Confluence Docker also [have an option to enable|https://hub.docker.com/r/atlassian/confluence-server/] it

            h3. Suggestion
            Enable the {{AccessLogValve}} by default for Confluence as it is important for Support during troubleshooting
            Damien Tan created issue -

              Unassigned Unassigned
              btan@atlassian.com Damien Tan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: