You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jmeter.apache.org by pm...@apache.org on 2017/02/11 09:34:27 UTC
svn commit: r1782564 - /jmeter/trunk/xdocs/extending/JMeter Extension
Scenario.xml
Author: pmouawad
Date: Sat Feb 11 09:34:27 2017
New Revision: 1782564
URL: http://svn.apache.org/viewvc?rev=1782564&view=rev
Log:
Update docs after migration to slf4j
Modified:
jmeter/trunk/xdocs/extending/JMeter Extension Scenario.xml
Modified: jmeter/trunk/xdocs/extending/JMeter Extension Scenario.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/extending/JMeter%20Extension%20Scenario.xml?rev=1782564&r1=1782563&r2=1782564&view=diff
==============================================================================
--- jmeter/trunk/xdocs/extending/JMeter Extension Scenario.xml (original)
+++ jmeter/trunk/xdocs/extending/JMeter Extension Scenario.xml Sat Feb 11 09:34:27 2017
@@ -167,22 +167,17 @@ extension.
<H2><A name="tips">Tips</A></H2>
<OL>
- <LI>You might consider using log4j as your logging utility since that's what
- JMeter uses. It's helpful for figuring out what's going on. Not all JMeter
- classes have been fully outfitted with logging statements. If things get
- nasty, you might have to add your own to JMeter and recompile it to see what
- is happening.
- <P>If you do decide to use log4j and you set the priority (or level, as it
+ <LI>You might consider using slf4j as your logging utility since that's what
+ JMeter uses. It's helpful for figuring out what's going on.
+ <P>If you do decide to use slf4j and you set the priority (or level, as it
will soon be called) to debug, you will probably see way more than you need to
- know. You can filter the JMeter stuff by making the following modifications to
- <TT>log4j.conf</TT> in the JMeter's <TT>bin</TT> directory. The <B>bold</B>
- text is added/modified <PRE> # Set the appenders for the categories
- log4j.rootCategory=<B>info</B>,Root_Appender
- <B>log4j.category.com.myfirm.jmeter=debug,</B>
- log4j.category.org.apache.jmeter.control=debug
- log4j.category.org.apache.jmeter.gui.tree.NonGuiTree=INFO,File_Appender
- </PRE>Note that the root (default) debugging has been set to <B>info</B>.
- This eliminates most log4j output from JMeter. The new line specifies the name
+ know. You can filter the JMeter stuff by adding to
+ <TT>log4j2.xml</TT> in the JMeter's <TT>bin</TT> directory.
+ <source>
+ <Logger name="com.myfirm.jmeter" level="debug" />
+ </source>
+ Note that the root (default) debugging has been set to <B>info</B>.
+ This eliminates most slf4j output from JMeter. The new line specifies the name
of the package containing JMeter extensions. (<TT>com.yourfirm.jmeter</TT>) in
this example. Note that it is not necessary to specify a particular class
name. Also, note that <B>no</B> appenders are specified - just the trailing