An Azure service that enables developers and testers to generate insights on how to improve the performance, scalability, and capacity usage of their application
You’re running a distributed JMeter test in Azure Load Testing and want a low-volume section to execute on only one engine. Azure Load Testing deploys the same JMX plan to every engine, and engine host names are implementation details, so branching on __machineName() is not a reliable allocation mechanism. For deterministic behavior, place that endpoint in a separate load test configured with one engine and coordinate its start with the main test. If one combined test is required, put the sampler under a Throughput Controller or Constant Throughput Timer and divide the intended aggregate rate by the configured engine count; every engine will contribute a small share, but the total rate is controlled. CSV split mode can distribute data rows among engines, yet it does not guarantee that a sampler runs on just one engine. Therefore, use a separate one-engine test when single-engine execution is a hard requirement.