Or: test plan - thread group - - SimpleController - - - sampler - - - sampler - - - aggregate - - SimpleController - - - sampler for tomcat status - - - sampler for another tomcat status - - - constant timer - - - monitor listener
-Mike On Fri, 2005-05-13 at 08:16 -0400, Peter Lin wrote: > just put the aggregate result in a different thread group. depending > on where you put the listener, it will aggregate the results > differently. for example, I usually do this > > test plan > - thread group > - - sampler > - - sampler > - - aggregate > - thread group (monitor > - - sampler for tomcat status > - - sampler for another tomcat status > - - constant timer > - - monitor listener > > > hope that helps > > peter > > > On 5/13/05, Guillaume Lahitette <[EMAIL PROTECTED]> wrote: > > report? > > X-Originating-Ip: 134.32.11.138 > > X-Originating-Server: ws6-3.us4.outblaze.com > > Message-Id: <[EMAIL PROTECTED]> > > X-Virus-Checked: Checked > > > > Folks, > > > > I am testing the Monitoring tool Peter has recommended me on the tomcat > > user list: > > http://jakarta.apache.org/jmeter/usermanual/build-monitor-test-plan.html. > > It is looking good so far. > > > > It triggered one question though. How can I exclude the monitoring results > > from the Aggregate Report? They are skewing the response times of my app. > > > > I currently do it when I paste the results in Excel...but I thought there > > might be a more automated way to do this. > > > > TIA > > Guillaume > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
