You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Anandkumar Natarajan <an...@jamcracker.com> on 2012/08/17 14:20:48 UTC

Configuration to get Transaction and Request level information without duplication

Hi,

Please suggest how to configure Jmeter to display information from Transaction Controller at "Summary Report" and "jp@gc - Transaction Throughput vs Threads" Listeners and at the same time display complete request level information at other listeners like "View Results Tree"

When Requests are grouped under Simple Controller, request level information is displayed at all listeners. This is too much of information for some of the reports that has to be shared with management hence grouped requests under Transaction Controller which solved the need. But this removed much needed information from other reports which are required to trouble shoot the bottleneck.

We could have two sets of scripts, one for management and other for engineering but execution and maintenance overheads creep_up and some intermediate issues are getting missed. Also for some reports like "jp@gc - Transaction Throughput vs Threads" if we don't use Transaction Controller then the graph is completely hidden with URL information.

Looking forward to your suggestions, thank you in advance.

Regards,
AK

Re: Configuration to get Transaction and Request level information without duplication

Posted by Philippe Mouawad <ph...@gmail.com>.
Jp@gc is not supported by Apache Jmeter.
Please redirect your question to the right mailing list.

On Friday, August 17, 2012, Anandkumar Natarajan wrote:

> Hi,
>
> Please suggest how to configure Jmeter to display information from
> Transaction Controller at "Summary Report" and "jp@gc - Transaction
> Throughput vs Threads" Listeners and at the same time display complete
> request level information at other listeners like "View Results Tree"
>
> When Requests are grouped under Simple Controller, request level
> information is displayed at all listeners. This is too much of information
> for some of the reports that has to be shared with management hence grouped
> requests under Transaction Controller which solved the need. But this
> removed much needed information from other reports which are required to
> trouble shoot the bottleneck.
>
> We could have two sets of scripts, one for management and other for
> engineering but execution and maintenance overheads creep_up and some
> intermediate issues are getting missed. Also for some reports like "jp@gc- Transaction Throughput vs Threads" if we don't use Transaction Controller
> then the graph is completely hidden with URL information.
>
> Looking forward to your suggestions, thank you in advance.
>
> Regards,
> AK
>


-- 
Cordialement.
Philippe Mouawad.