-
Suggestion
-
Resolution: Low Engagement
-
None
-
9
-
15
-
We've got an extremely busy 100-agent server, and we try not to restart it for extended periods of time if we can avoid it.
The Bamboo server process redirects all output to <BAMBOOINSTALLDIR>/logs/bamboo.log
This single log file will be populated without limit until the next time Bamboo is restarted, at which point it will be over-written completely.
There's two problems that need addressing:
- Restarting Bamboo should not wipe out the the existing logs. Right now we have to remember to copy the log before we start Bamboo so as we don't lose it.
- Bamboo is run via the Tanuki wrapper, but bamboo.sh over-rides any logging properties that are set in <BAMBOOINSTALLDIR>/conf/wrapper.conf. We really want to have great control over log roll-over, and wrapper.conf is the most appropriate method to do this. Because all logging is in a single enormous bamboo.log, it makes analysing it and sending it to Atlassian Support a major PITA if the log is a few days old. We really want to be able to roll-over daily.
[BAM-11246] bamboo.sh over-rides wrapper logging settings preventing <BAMBOOINSTALL>/logs/bamboo.log customization
Paul Ellis
added a comment - Actually, it looks like the log is being written to both <bamboo install>/atlassian-bamboo.log and <bamboo install>/logs/bamboo.log, the later had reached 4Gbyte, the former is being rolled around but the application still reports "can't find log in current directory" whereever that is.
Paul Ellis
added a comment - Actually, it looks like the log is being written to both <bamboo install>/atlassian-bamboo.log and <bamboo install>/logs/bamboo.log, the later had reached 4Gbyte, the former is being rolled around but the application still reports "can't find log in current directory" whereever that is. Paul Ellis
added a comment - We are also experiencing this. The log file is <bamboo install>/logs/bamboo.log even though the application and documentation seem to be expecting the log file in <bamboo install>/atlassian-bamboo.log
Paul Ellis
added a comment - We are also experiencing this. The log file is <bamboo install>/logs/bamboo.log even though the application and documentation seem to be expecting the log file in <bamboo install>/atlassian-bamboo.log 
Jan Swaelens
added a comment - We are also experiencing trouble with this feature, the log is growing GB's big which is causing a disk space issue.
Would be great if this was tackled!
Jan Swaelens
added a comment - We are also experiencing trouble with this feature, the log is growing GB's big which is causing a disk space issue.
Would be great if this was tackled!
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Bamboo Data Center, please check our public roadmap.
Kind regards,
Bamboo Data Center