All Versions
Bamboo 5.13Bamboo 5.7.x
Bamboo 5.6.x
More...
There are two distinct logs generated by Bamboo:
xml-data/builds/ sub-directories. The build logs can be downloaded as an artifact from the Viewing a Build's Artifacts page in Bamboo.<Bamboo-Install> directory or the directory you started Bamboo from. If you are running Bamboo as a service on windows, the logs are generated in the <Bamboo-Install>/log folder.Bamboo uses the log4j library for logging during runtime. The logging levels can be changed by editing the <Bamboo-Install>/webapp/WEB-INF/classes/log4j.properties file. There are four logging levels available: 'INFO', 'DEBUG', 'ERROR' and 'FATAL'.
The rootLogger property controls the verbosity of logs being generated at the top level. By default, the root level logging is set to 'INFO'. To change the root level logging, follow the steps below:
<Bamboo-Install>/webapp/WEB-INF/classes/log4j.properties file:
# # Change the following line to configure the bamboo logging levels (one of INFO, DEBUG, ERROR, FATAL) # log4j.rootLogger=INFO, console, filelog
log4j.rootLogger to the desired logging level.By default, the atlassian-bamboo logs can either be found either in the root <Bamboo-Install> directory or the directory you started Bamboo from. In case of a Tomcat webapp deployment, the logs are piped out to catalina.out file.
To change the directory that the atlassian-bamboo logs are generated to, you must set the environment variable for the target location of the logs, as seen below:
log4j.appender.fileLog.file=/my/path/to/atlassian-bamboo.log
Note that the new log file location applies to both the server and remote agents. If using an absolute path this may result in aggregated logs.