Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-67796

Don't log Jira events to STDOUT - catalina.out

    XMLWordPrintable

Details

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      Problem Definition

      Currently, Jira logs all events 2x times to Log4j file and STDOUT (catalina.out).
      That uses 2x space and creates extra load for the disk (see JRASERVER-28941).

      Suggested Solution

      Don't log Jira events to STDOUT

      • Keep those loggers for the supportability:
        • log4j.logger.com.atlassian.upgrade
        • log4j.logger.com.atlassian.jira.upgrade
        • log4j.logger.com.atlassian.jira.startup
        • log4j.logger.com.atlassian.jira.config.database
      • Increase the number of atlassian-jira.log files from 5 to 10 to compensate the change

      Workaround

      • Remove all console from log specific logging events, see examples
        -log4j.logger.com.atlassian = WARN, console, filelog
        +log4j.logger.com.atlassian = WARN,  filelog
         log4j.additivity.com.atlassian = false
        

        sed code:

        sed '230,$s/console,//' ./log4j.properties > ./log4j.properties_new
        

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              ayakovlev@atlassian.com Andriy Yakovlev [Atlassian]
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: