On 16/05/2008, Laurent Perez <[EMAIL PROTECTED]> wrote: > > > > If the Java sample request returns a null sample, then there's nothing > > to collect. > > > > unfortunately, my sample is returning data, so I'll just move it to another > instance as you suggested and postpone the start of the first instance to > let me start the second instance by hand. >
Just had another thought: there is a summariser: http://jakarta.apache.org/jmeter/usermanual/component_reference.html#Generate_Summary_Results which aggregates statistics by the value of the Name: field, so you could add it to just the thread groups you want to monitor. However, the output is designed for batch runs, so may not be suitable. If you don't mind waiting until the end of the run, you could filter the the JTL files to remove the extra data and then load into the Summary Report. Or use mutiple Summary Reports and combine the data afterwards. You can select the table cells and copy and paste the data into a spreadsheet. (Next version of JMeter will have a Save button). Or indeed, do your own analysis on the JTL files. All depends what you need the report for. > thanks > laurent > > > > > > > > > > thanks > > > laurent > > > > > > > > > > > > -- > > > <a href="http://in-pocket.blogspot.com";>http://in-pocket.blogspot.com - > > > Mobile world, technology and more</a> > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > > <a href="http://in-pocket.blogspot.com";>http://in-pocket.blogspot.com - > Mobile world, technology and more</a> > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
