On 5/30/05, Sonam Chauhan <[EMAIL PROTECTED]> wrote: > > Have you tried using the same filename for both logs? > > Thank you Seb. I tried that and it logs failures twice in the JMeter log. > > Actually, let me correct a faulty assumption I made - I expected the > assertion listener (setup as I described) to be the only thing logging > request/response data. But in functional test mode, the regular JMeter log > records request/response data for *all* requests - whether succeeded or > failed. So there is no advantage to having a separate assertion listener > logfile. > > Can we restrict "functional test logging" to failed requests only? i.e. The > test runs at full speed with the default logging, and only logs the detailed > request/response data for sampler that fail. Is this possible?
I added this property to CVS HEAD recently: jmeter.save.saveservice.response_data.on_error I think that does what you want. S. > Regards, > Sonam Chauhan > -- > Electronic Commerce, Corporate Express Australia Ltd. > Phone: +61-2-9335-0725, Email: [EMAIL PROTECTED] > > > > -----Original Message----- > > From: sebb [mailto:[EMAIL PROTECTED] > > Sent: Saturday, 28 May 2005 6:10 PM > > To: JMeter Users List > > Subject: Re: How to correlate debug error data with JMeter logs? > > > > Have you tried using the same filename for both logs? > > > > S. > > On 5/26/05, Sonam Chauhan <[EMAIL PROTECTED]> wrote: > > > Hi JMeter users- > > > > > > I want to capture the exact sampler request and response data when a > > failure > > > occurs, and correlate it with JMeter log entries. Can I have your > > feedback > > > on this? > > > > > > Here is what I do: > > > 1. In the uppermost test plan element, tick 'Functional Test Mode' > > > 2. In the bottom outer level, insert an 'Assertion Listener'. > > > At this position, it can "listen" to all samplers. > > > 3. Set these 'Assertion Listener' properties: > > > a. Write all data to a logfile > > > b. Tick 'Log Errors Only' (to reduce the logging overhead) > > > > > > After the test runs, I get two logfiles: > > > a. JMeter logfile (-l parameter) > > > This logfile contains the usual brief log entries for all samplers that > > ran. > > > > > > b. 'Assertion Listener' logfile (Specified in > > > This contains entries similar to the JMeter log, but only for assertion > > > failures, and with extra tags (e.g.: <binary>) that carry sampler > > request > > > and response data. > > > > > > A few questions: > > > * How can I correlate the 'Assertion Listener' failure data with > > the > > > JMeter log entries? > > > If common GUIDs were assigned to logentries, this would be easy, but > > there > > > aren't > > > > > > * Can the 'Assertion Listener' logfile be set to not only store > > debug > > > error data, but also store brief entries for all requests? > > > This would put all the required data in one file - there would be no > > need to > > > correlate with the JMeter logfile. > > > > > > * Can this be done better another way? > > > > > > Sincerely, > > > Sonam Chauhan > > > -- > > > Electronic Commerce, Corporate Express Australia Ltd. > > > Phone: +61-2-9335-0725, Email: [EMAIL PROTECTED] > > > <mailto:[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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
