An Azure service that enables developers and testers to generate insights on how to improve the performance, scalability, and capacity usage of their application
Azure stores detailed debug artifacts separately. The normal Results CSV follows the JMeter CSV format and contains fields such as response code, response message, URL, timing, and failure message—not full request or response bodies.
Open the exact run and confirm Debug mode. Export that run’s results, then inspect the per-engine debug files in its storage container rather than only the CSV or worker log. Debug mode captures request and response data only for failed application requests, so successful samples will not contain bodies. A failure that occurs before an HTTP sample is sent, such as script loading, DNS, or missing-file failure, also has no HTTP response to capture. Re-run with one failing sampler, one engine, and under ten minutes. If the debug artifacts are absent for a genuine failed HTTP response, preserve the run ID and raise a Load Testing support case.