This post is based on the assumption that you have JMeter and Fiddler installed and a basic knowledge around how to use JMeter.
Fiddler and JMeter
In some cases when you are scripting something quite complicated you might just need a bit of extra information on the requests that you are making. I’ve used Fiddler a lot in the past to trace back requests and it turns out there is an easy way to integrate this with JMeter.
Fiddler works by placing a proxy between the requests you make and the internet, it does this automatically when you start it up. The default proxy address is 127.0.0.1 (i.e. your local machine) across port 8888. For more info about Fiddler take a look at http://www.fiddler2.com/fiddler2/
Now all you need to do is get JMeter to send all its traffic through this proxy. To do this, navigate to your JMeter bin directory either in command line or through run and enter the following:
jmeter.bat –H 127.0.0.1 –P 8888
Hit run or enter and you should be able to use JMeter as normal.
Now with fiddler running you should be able to see your requests being made and that extra detail that you’ve been looking for:
Note that the above uses fiddler but this technique can be used with different proxies to gather the information or emulate what you are looking for. You can do this by using the following commands after jmeter.bat
-H [IP address of your proxy server]
-P [port number of your proxy server]
-N [Non proxy hosts could be ‘localhost’ or something like ‘*.apache.org’]
-u [Username for proxy authorisation (optional)]
-a [Password for proxy authorisation (optional)]
You should now be able to let your proxy pick up all requests made from your script(s) which should make life just that bit easier.
About the author
Team Capacitas
FinOps and AI: Building the Financial Discipline for the Next Wave of Enterprise Intelligence
AI FinOps represents an evolution rather than a replacement of traditional FinOps. It extends the model into a domain where financial, technical, and product decisions are tightly interconnected.
Confidence Under Load: How We Verified AKS Readiness for Peak
How Capacitas verified AKS readiness for peak demand by validating workload performance, autoscaling, cluster capacity, monitoring, and incident response.
Building Cloud Resilience: Lessons from the AWS Outage
Learning from the Latest Outage. Events like this week’s AWS disruption highlight one clear truth: resilience must be designed, not assumed.
Bringing Order to Chaos: A Practical Guide to Chaos Testing in the Cloud
In today’s cloud-native environments, resilience is not optional—it’s critical. Chaos testing has emerged as a key practice for validating system behaviour under failure conditions.
