Log Levels
How To <overrideRootLogLevel>
You can specify a root log level for debug purposes.
+---+
<project>
[...]
<build>
<plugins>
<plugin>
<groupId>com.lazerycode.jmeter</groupId>
<artifactId>jmeter-maven-plugin</artifactId>
<version>2.0.3</version>
<executions>
<execution>
<id>jmeter-tests</id>
<goals>
<goal>jmeter</goal>
</goals>
</execution>
</executions>
<configuration>
<overrideRootLogLevel>debug</overrideRootLogLevel>
</configuration>
</plugin>
</plugins>
</build>
[...]
</project>
+---+
Setting the root log level will always override any settings for individual category log levels (as a result if the <overrideRootLogLevel> is set all category log levels set elsewhere will be ignored.
Advanced Log Configuration
If you add a "logkit.xml" into the <testFilesDirectory> it will now be copied into the /bin folder. If one does not exist the default one supplied with JMeter will be used instead. If you don‘t want to call your advanced log config file "logkit.xml", you can specify the filename using:
+---+
<project>
[...]
<build>
<plugins>
<plugin>
<groupId>com.lazerycode.jmeter</groupId>
<artifactId>jmeter-maven-plugin</artifactId>
<version>2.0.3</version>
<executions>
<execution>
<id>jmeter-tests</id>
<goals>
<goal>jmeter</goal>
</goals>
</execution>
</executions>
<configuration>
<logConfigFilename>myFile.xml</logConfigFilename>
</configuration>
</plugin>
</plugins>
</build>
[...]
</project>
+---+
Individual Log Levels
You can override individual log levels by setting them in your jmeter.properties file. If you want to override them in the POM have a look at Adding Additional Properties To <propertiesJMeter>.