Configure log4j level in Build Logs (particularly apache.http.wire)

Answered

Hello,

As part of a build step, the artefacts I have built in TeamCity are streamed to our deployment tool using the notoriously verbose classes in apache.http.wire.*.

These classes are producing a huge amount of DEBUG logging and the resultant TeamCity build logs are becoming too unwieldy to view.

Is there some way to configure the log4j settings for these build logs, which will filter down to these third party classes?

I've tried adding the following lines to /data/teamcity/application/conf/teamcity-server-log4j.xml:

<filter class="org.apache.http.wire">
  <param name="LevelMin" value="WARN"/>
</filter>

but so far nothing has made an impact.

Am I looking in the right place for this configuration?

Many thanks

0
1 comment

Hello Ryan,

The log4j file is used to configure TeamCity server logs, not build log. If you want to reduce the build log size, please tune the build scripts not to print too much into the output.

0

Please sign in to leave a comment.