Skip to main content

Processing JMeter Results using awk

awk is Pattern scanning and processing language. Its name is derived from its authors “Aho, Weinberger, and Kernighan”.
Some of its features are:
  • Awk views a text file as records and fields
  • Awk has variables, conditionals and loops
  • Awk has arithmetic and string operators
  • Awk can generate formatted reports
Syntax:
awk '/search pattern1/ {Actions}
    
/search pattern2/ {Actions}' file
Herein :
  • search pattern is a regular expression.
  • Actions – statement (s) to be performed.
  • several patterns and actions can be used in Awk.
  • file is the Input file.
  • Single quotes around program avoids shell interpreting any special characters.


Let’s Consider following jmeter summary file -


summary +    41 in  15.4s =    2.7/s Avg:  2234 Min:   383 Max:  6974 Err: 0 (0.00%)
summary +    57 in  21.5s =    2.6/s Avg:  2548 Min:   618 Max:  4528 Err: 0 (0.00%)
summary =    98 in  32.5s =    3.0/s Avg:  2416 Min:   383 Max:  6974 Err: 0 (0.00%)
summary +   108 in  21.8s =    5.0/s Avg:  1291 Min:   229 Max:  6317 Err: 0 (0.00%)
summary =   206 in  52.5s =    3.9/s Avg:  1827 Min:   229 Max:  6974 Err: 0 (0.00%)


Let’s assume that we want to print lines where avg response time is more than 2500ms
awk '{if($9>2500){print $0}}' file.txt


Herein $9 is the the 9th field in log file and $0 denotes all of record


Hence we would get following output -
summary +    57 in  21.5s =    2.6/s Avg:  2548 Min:   618 Max:  4528 Err: 0 (0.00%)


Or printing the records with avg response time more than 2400ms


awk '{if($9>2400){print $0}}' file.txt


And we would get following output -


summary +    57 in  21.5s =    2.6/s Avg:  2548 Min:   618 Max:  4528 Err: 0 (0.00%)
summary =    98 in  32.5s =    3.0/s Avg:  2416 Min:   383 Max:  6974 Err: 0 (0.00%)


Find the total number of record in jmeter.log file -


wc file.txt | awk ‘{print $0}’


Consider that you are logging custom variables on Jmeter log file (i.e. email address etc) and now you want to figure out which email address caused higher latency. Can you guess how you can achieve it?

Popular posts from this blog

Appium and android mobile app automation

Next appium and Android mobile app automation video tutoria l is live. If you are new to appium then please check - appium-tutorial This video tutorial covers - Start vysor (Just for this session and not mobile automation :)) Start appium and start appium inspector Desired Capabilities platformName - Android deviceName - L2N0219828001013 (as seen on "adb devices") Saved Capability Sets Start Session Scan app elements using appium inspector Get appPackage and appActivity using "APK info" app Install "APK info" app and open app whose appPackage and appActivity are required i.e. calculator Check top section of app icon com.android.calculator2 is app package com.android.calculator2.Calculator is app activity testng.xml file settings for running Android app tests Test details com.seleniumtests.tests.mobile.AndroidAppTest and CalculatorScreen class View beautiful STF test report  

Verify email confirmation using Selenium

Note: If you are new to java and selenium then start with selenium java training videos .     Email confirmation seems to be integral part of any registration process. I came across an application which lets you provide your email address. You can follow the sign up link in you mail and then complete the registration process. Lets consider we provide GMail address for it. Now if were to use only Selenium then we would have to follow following steps - Launch GMail using Selenium; Some how search for new mail in the list of available mails; Some how click on it; Parse the mail message; Get the registration link; Follow up with registration process What do you think of an approach in which you can

Selenium Tutorial: Ant Build for Selenium Java project

Ant is a build tool which could be used to have your tests running either from command line or from Hudson CI tool. There is detailed documentation available for ant here but probably you need to know only a little part of it for you selenium tests. The essentials which are needed to know are: Project Target (ant execution point and collection of tasks) Tasks (could be as simple as compilation) And there would usually be following targets for Selenium tools - setClassPath - so that ant knows where you jar files are loadTestNG - so that you could use testng task in ant and use it to execute testng tests from ant init - created the build file clean - delete the build file compile - compiles the selenium tests run - executes the selenium tests Here is my project set up for ant -