Is there a simple way to control the logging level of JMeterPluginsCMD ?

[J]

Hi All,

Prior to version 1.1.1 or 1.1.2 of JMeterPluginsCMD was printing just a scarce log like the one below:

DEBUG   2013-10-15 07:15:13.139 [kg.apc.j] (): Creating jmeter env using JMeter home: /srv/jenkins/jobs/.../workspace/apache-jmeter-2.9

And now it gives much more verbose output when generating the graphs:

INFO    2013-10-29 11:17:50.107 [kg.apc.j] (): Using JMeterPluginsCMD v. 1.1.2
INFO    2013-10-29 11:17:50.143 [jmeter.u] (): Setting Locale to en_GB
INFO    2013-10-29 11:17:50.193 [kg.apc.j] (): Loading user properties from: /srv/jenkins/jobs/...../workspace/apache-jmeter-2.10/bin/user.properties
INFO    2013-10-29 11:17:50.194 [kg.apc.j] (): Loading system properties from: /srv/jenkins/jobs/..../workspace/apache-jmeter-2.10/bin/system.properties
INFO    2013-10-29 11:17:51.116 [jmeter.s] (): Testplan (JMX) version: 2.2. Testlog (JTL) version: 2.2
INFO    2013-10-29 11:17:51.123 [jmeter.s] (): Using SaveService properties file encoding UTF-8
INFO    2013-10-29 11:17:51.131 [jmeter.s] (): Using SaveService properties version 2.5
INFO    2013-10-29 11:17:51.137 [jmeter.s] (): Using SaveService properties file version 1519088
INFO    2013-10-29 11:17:51.151 [jmeter.s] (): All converter versions present and correct
INFO    2013-10-29 11:17:51.155 [jmeter.s] (): Note: Sample TimeStamps are START times
INFO    2013-10-29 11:17:51.155 [jmeter.s] (): sampleresult.default.encoding is set to ISO-8859-1
INFO    2013-10-29 11:17:51.155 [jmeter.s] (): sampleresult.useNanoTime=true
INFO    2013-10-29 11:17:51.155 [jmeter.s] (): sampleresult.nanoThreadSleep=5000
INFO    2013-10-29 11:17:51.161 [jmeter.s] (): List of sample_variables: []
INFO    2013-10-29 11:17:51.593 [kg.apc.c] (): Saving PNG to /srv/jenkins/jobs/..../workspace/projects/.../results/imgs/node0-LatenciesOverTime.png

Is there a simple way to control the logging level of JMeterPluginsCMD ? 

For example JMeter allows you to control it by using the "-L" param (-LDEBUG, -LINFO etc)

btw. I also updated JMeter to 2.10 when I updated JMeter-Plugins to 1.1.1, maybe it has something to do with it?

Cheers,

Janusz

[Andrey Pohilko]

Hi, Janusz,

I'd to say that second logging example is more of what I expect from the code. The logging is initiated almost the same way as JMeter do. Logging levels for individual classes and packages should be configurable via jmeter.properties files.

Finally, the quick way to change console logging level is "--loglevel WARN" with DEBUG/INFO/WARN/ERROR as a level parameters. This came from CMDRunner.jar

вторник, 29 октября 2013 г., 16:52:33 UTC+4 пользователь J написал:

[J]

Hi Andrey,

I modified the log_level.jmeter in the jmeter.properties and set the --loglevel for CMDRunner.jar to my liking and everything worked like a charm :) 

Thank you,

Janusz