Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-28941

Ship JIRA with defaults that enable log rotation

XMLWordPrintable

    • 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.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Atlassian Update - 22 April 2015

      Hi everyone,

      Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with JIRA.

      At this time, this suggestion is not on the JIRA development roadmap. Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Dave Meyer
      dmeyer@atlassian.com
      Product Manager, JIRA Platform

      I understand that there are limitations to logging based on log4j and in Tomcat but it is a pain for an Administrator, and for Atlassian support engineers to work with massive logfiles. JIRA should ship with a logging system which has log rotation enabled by default for more than just instance restarts.

      Workaround

      Choose one them:

      • Options to rotate the catalina.out and detailed steps for using logrotate are documented at How to Rotate the Catalina Log File.
      • Increase logging level for console loggers to WARN and restart JIRA, see diff: 
        diff -u ./atlassian-jira-6.4.13-standalone//atlassian-jira/WEB-INF/classes/log4j.properties  ./log4j.properties
--- ./atlassian-jira-6.4.13-standalone//atlassian-jira/WEB-INF/classes/log4j.properties	2016-02-25 06:10:30.000000000 +0100
+++ ./log4j.properties 	2016-09-26 15:51:16.000000000 +0200
@@ -28,12 +28,12 @@
 #####################################################

 log4j.appender.console=org.apache.log4j.ConsoleAppender
-log4j.appender.console.Threshold=DEBUG
+log4j.appender.console.Threshold=WARN
 log4j.appender.console.layout=org.apache.log4j.PatternLayout
 log4j.appender.console.layout.ConversionPattern=%d %t %p %X{jira.username} %X{jira.request.id} %X{jira.request.assession.id} %X{jira.request.ipaddr} %X{jira.request.url} [%c{4}] %m%n

 log4j.appender.nowarnconsole=org.apache.log4j.ConsoleAppender
-log4j.appender.nowarnconsole.Threshold=DEBUG
+log4j.appender.nowarnconsole.Threshold=WARN
 log4j.appender.nowarnconsole.layout=org.apache.log4j.PatternLayout
 log4j.appender.nowarnconsole.layout.ConversionPattern=%d %t %p %X{jira.username} %X{jira.request.id} %X{jira.request.assession.id} %X{jira.request.ipaddr} %X{jira.request.url} [%c{4}] %m%n
      • 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

              Unassigned Unassigned
              bberenberg Boris Berenberg (Inactive)
              Votes:
              190 Vote for this issue
              Watchers:
              120 Start watching this issue

                Created:
                Updated:
                Resolved: