Thank you. > The CSV data file by default includes the sampler label in each record. Yes, agreed.
I use the jmeter proxy to record the test. The sampler label name (in the csv file) is generated by jmeter and is usually equal to the first part of the url. I use the jmeter feature to add numeric prefix. This ensures each sampler label name is unique in the csv. Jmeter names the transaction controller the same as the first sampler in its group: 1 SAMPLERblah (transaction controller) 1 SAMPLERblah 2 SAMPLER 3 SAMPLER ... 55 SAMPLERyyy (transaction controller) 55 SAMPLERyyy 56 SAMPLER 57 SAMPLER ... 110 SAMPLERxxx (transaction controller) 110 SAMPLERxxx 111 SAMPLER 112 SAMPLER ... In the result csv there can be thousands of rows, each row represents sampler data or a transaction summary. The sampler rows do not contain the name of the transaction they were a part of. There is not a column that equals the transaction name, afaik. So, that is what I am looking for: the transaction controller name. Any ideas how to get this? ---- sebb <[email protected]> wrote: > On 28 July 2015 at 15:41, Onl <[email protected]> wrote: > > Hi, > > Reposting and rephrasing, hopefully a clearer question. > > > > We are analysing the csv data file. > > Is there any way to know what transaction controller group a given sampler > > (http request ) > > is from? > > The CSV data file by default includes the sampler label in each record. > This can be used to tie the sample to the sampler and therefore the TC > group that includes it. > > If your test plan has multiple samplers with the same label, you will > need to use additional context (e.g. the neighbouring sample labels in > the same thread) in order to disambiguate the sample. > > It helps to have a clear convention for naming samplers and > controllers when creating test plans that have lots of samplers. > > > Thanks. > > > > --------------------------------------------------------------------- > > 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]
