The information on this page relates to the Bamboo server (atlassian-bamboo) logs only. You cannot change the logging configuration for the build logs. 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. 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-agent.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. 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.

始める前に

• Note, you will not need to restart your Bamboo server for any logging changes to take effect.

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.

Screenshot above: 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. 対象のリモート エージェント用に log4j.properties ファイルを設定します。任意の log4j.properties ファイルを使用できます。log4j.properties ファイルがまだない場合は、サーバーから log4j.properties ファイルのコピーを取得し、それをリモート エージェントにコピーして希望どおりに設定できます。

   • log4j.properties ファイル内の rootLogger プロパティは、ルート レベルで生成されるログの詳細度を制御するためのものです。既定では、ルート レベルのロギングは「INFO」に設定されています。ルート レベルのロギングを変更するには、<Bamboo-Install>/webapp/WEB-INF/classes/log4j.properties ファイル内の次の行を探し、log4j.rootLogger の値を目的のログ レベルに更新します。

     # # 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. リモート エージェントの log4j.configuration システム プロパティを更新して、log4j.properties ファイルを指すようにします。そのためには、<bamboo-agent-home>/conf/wrapper.conf ファイルに次の行を追加します。
   

   wrapper.java.additional.3=-Dlog4j.configuration=/full/path/to/log4j.properties

   ここで、/full/path/to/log4j.properties は、log4j.properties ファイルの絶対パスです。
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.

注意

関連トピック

Configuring System Settings
Locating Important Directories and Files
Viewing a Build's Artifacts