How to find the time web_submit_data event happened
We are using LoadRunner 11.04 and need to find the time a particular web_submit_data event happened. Is there a way this can be scripted? Any help is appreciated.
You could capture the time using a LoadRunner parameter. Use a date/Time parameter and then call it immediately before the web_submit_data, outputting it a log or to a transaction name or something. This wont give u the exact millisecond of execution but pretty close. I'm not sure if that's the best way either, but that's how I would do it.
Or..just had another idea. You could put an empty start and end transaction marker right before the web_submit_data, giving it a unique transaction name, and then you'll know based on the analysis the rough time the transaction occured.
Placing transaction markers is best option to get timing of the event. You can make use of lr_wasted_time to move wasted time for that particular event and compute exact response time.
If you are trying to find when a particular transaction (for example a very slow one) occured during a test quite accurately - then the raw data out of analysis could be an excellent place to look - you get a timestamp for the response, down to hundredths of a second from the start of the test, on the same line as Transaction Response Time and Transaction Name - to get the start of the request subtract the response time from the scenario elapsed time and add to the start time of the test
There are several ways which require zero code inclusion
(1) Look at your web server logs. Time is to the millisecond of precision for logs events
(2) Every transaction is recorded to the millisecond offset from the start of the test. So, if you know the start you can then get the precise system time of an event. Take a look at the generated Microsoft Access formatted datafile for the results and you should be able to find the events in the [event meter] table as well as information on the time of the results and the related transaction name. If you have monitor data you can then write you own queries to pull information on monitors and transactions in the window of +/- 30 seconds from your interesting event
Minimal code? try lr_output_message() which will put a message to the output window of the controller during the test. These are all time stamped and you can export the information at the end of the test. You can also pull information from the output.mdb file directly at the conclusion of the test if you have already shut down the controller.
Replace ineffective offshore contracts, LoadRunnerByTheHour
. Starting @ $19.95/hr USD.
Put us to the test, skilled expertise is less expensive than you might imagine.
Twitter: @LoadRunnerBTH @PerfBytes