TeamCity uses Log4J for internal logging of events. The following logging rules are used:
For additional option on logging tweaking please consult Reporting Issues section.
TeamCity server logs
Default TeamCity server Log4J configuration file is <TeamCity home>/conf/teamcity-server-log4j.xml
TeamCity server logs are placed to <TeamCity home>/logs directory and prefixed with teamcity- prefix.
Log Files
| File name |
Description |
| teamcity-server.log |
General server log |
| teamcity-activities.log |
Log of build starting and user-initiated events |
| teamcity-vcs.log |
Log of VCS-related messages |
| teamcity-svn.log |
(off by default) SVN integration log |
| teamcity-tfs.log |
(off by default) TFS integration log |
| teamcity-starteam.log |
(off by default) StarTeam integration log |
| teamcity-clearcase.log |
(off by default) ClearCase integration log |
| teamcity-performance.log |
(off by default) Performance-related log |
| teamcity-ldap.log |
(off by default) LDAP-related log |
You can configure location of the logs by altering the value of teamcity_logs property (passed to JVM via -D option).
You can also change Log4J configuration file location by changing value of log4j.configuration property.
See corresponding documentation section on how to pass the options.
If you used the WAR-distribution to install TeamCity, by default you should be able to find teamcity.log file in the <J2EEContainer>/logs directory.
To use default settings if you start the web server using your own script make sure you pass the following JVM options:
Build agent logs
Default build agent Log4J configuration file is <agent home>/conf/teamcity-agent-log4j.xml
Build agent logs are placed into <agent home>/logs directory.
Log Files
| File name |
Description |
| teamcity-agent.log |
General build agent log |
| teamcity-build.log |
stdout and stderr output of builds run by the agent |
| upgrade.log |
log of the build agent upgrade (logged by the upgrading process) |
| launcher.log |
log of the agent's monitoring/launching process |
| wrapper.log |
(only present when the agent is run as Windows service or by Java Service Wrapper) output of the process build agent launching process |
You can configure location of the logs by altering the value of teamcity_logs property (passed to JVM via -D option).
You can also change Log4J configuration file location by changing value of log4j.configuration property.
See corresponding documentation section on how to pass the options.
