This documentation relates to an earlier version of Bamboo.
View

Unknown macro: {spacejump}

or visit the current documentation home.

Bamboo では次の 2 種類のログ セットが生成されます。

  • Build Logs: The build logs are generated each time a plan is executed. All information specific to the build is stored in these logs. The build logs are located in the <Bamboo-Home>/xml-data/builds/ sub-directories. The build logs can be downloaded as an artifact (see Viewing a Build's Artifacts).
  • atlassian-bamboo Logs:
    • atlassian-bamboo Logs for the Bamboo Server — Bamboo records all server activity in the atlassian-bamboo.log. The location of the atlassian-bamboo.log file can be viewed in Bamboo's System Information under the 'Bamboo Paths' section. The location will generally be either 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.
      (info) Please note, this log is different to the bamboo.log found in the <Bamboo-Install>/logs directory, which is the log written by the Java Service wrapper.
    • atlassian-bamboo Logs for Remote Agents — All agent activity is recorded in atlassian-bamboo.log file stored on the agent machine. These are generated in the running directory of the agent. The running directory can be viewed in the remote agent's system properties under the 'Bamboo Paths' section.
    • atlassian-bamboo Logs for Elastic Agents — Elastic agent activity is logged inside the elastic instance where the elastic agent runs. To access the elastic agent logs (atlassian-bamboo.log and bamboo-elastic-agent.out) use ssh to log in to your elastic instance as described in Viewing an Elastic Instance and retrieve the logs.

See Locating Important Directories and Files for information on where to find other important files in Bamboo.

The information below relates to the Bamboo server (atlassian-bamboo) logs only. You cannot change the logging configuration for the build logs.

On this page:

Configuring the Level of Logging

 

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 five logging levels available: 'DEBUG', 'INFO', 'WARN', 'ERROR' and 'FATAL'. Each logging level provides more logging information that the level before it:
DEBUG < INFO < WARN < ERROR < FATAL
i.e. DEBUG provides the most verbose logging and FATAL provides the least verbose logging.

Configuring the Level of Logging on your Bamboo Server

You can adjust the logging levels for the different Bamboo packages on the fly, using the runtime log4j configuration tool in the Bamboo administration console. The default log settings are still stored in the log4j.properties file. When you view the log settings page for the first time you will see the default log settings as defined in log4j.properties. All changes to the log settings via the runtime log4j configuration tool will not be persisted and are valid during bamboo runtime only.

To change the level of logging on your Bamboo server,

  1. Click the 'Administration' link in the top navigation bar.
  2. Click the 'Log Settings' link in the left navigation column under the 'System' section. The 'Bamboo Log Settings' page will display showing the Bamboo packages being logged (see screenshot below).
    • To change the logging level of a package that is already being logged, locate the Bamboo package, select the desired logging level from the dropdown next to it and click 'Save'.
    • To start the monitoring a package in the Bamboo logs, enter the class name in the text box at the top of the page, select the desired logging level from the dropdown next to it and click 'Add'.
    • To stop logging a package, locate the Bamboo package and click the 'Delete' link next to it.

(info) Note, you do not need to restart your Bamboo server for the logging changes to take effect.

Screenshot: Bamboo Log Settings

Configuring the Level of Logging on your Bamboo Remote Agents

Bamboo 管理コンソールのランタイム log4j 設定ツールは、Bamboo Server のログ レベルの変更にのみ使用できます。リモート エージェントのログ レベルを設定するには、log4j.properties ファイルを手動で更新する必要があります。

各リモート エージェントのロギングは、Bamboo Server とは別に制御できます。そのためには、複数のリモート エージェントに対して下記のプロセスを繰り返し、各リモート エージェントの log4j.propertiesファイルによって Bamboo Server 上の log4j.propertiesファイルをオーバーライドするだけです。

To change the level of logging on your remote agent,

  1. Configure a log4j.properties file for your remote agent. This can be any log4j.properties file. If you do not already have a log4j.properties file, you can take a copy of the log4j.properties file from the server, copy it to your remote agent and configure it as desired:
    • The rootLogger property in the log4j.properties file 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, find the following lines in <Bamboo-Install>/webapp/WEB-INF/classes/log4j.properties file and update the value of log4j.rootLogger to the desired logging level: 
      #
# Change the following line to configure the bamboo logging levels (one of INFO, DEBUG, ERROR, FATAL)
#
log4j.rootLogger=INFO, console, filelog
    • 必要に応じて、次のように、log4j.properties で個々のパッケージのログ レベルを変更します。log4j.category.webwork=WARN
  2. ファイルの変更を保存します。
  3. Update the log4j.configuration system property on your remote agent to point to the log4j.properties file. To do this, add the following command line parameter when starting your remote agent:
    -Dlog4j.configuration=/path/to/log4j.file
    where /path/to/log4j.file is the absolute path of your log4j.properties file. You can also update this setting in the bamboo-agent.cfg.xml file.
  4. リモート エージェントを再起動します。

Configuring the Location of the atlassian-bamboo Logs

 

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.

  • ラベルなし



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.