1. JMeter doesn't know anything about your application infrastructure, when it comes to load testing load balanced applications it's a good idea to add DNS Cache Manager <https://jmeter.apache.org/usermanual/component_reference.html#DNS_Cache_Manager> to your Test Plan so each thread (virtual user) would resolve the IP address of load balancer on its own. Also if there is some form of session stickiness <https://www.imperva.com/learn/availability/sticky-session-persistence-and-cookies/> you can trace down the relevant HTTP Header or part of the URL. If you need insights what happens under the hood of your application infrastructure during the load test you should go for an APM tool <https://www.blazemeter.com/blog/getting-the-full-application-picture-with-blazemeter-and-apm-integration>
2. JMeter automatically aggregates all the results no matter of the origin (thread group), if you need to have ability to distinguish results coming from different thread groups you can use __threadGroupName() <https://jmeter.apache.org/usermanual/functions.html#__threadGroupName> function for this -- Sent from: http://www.jmeter-archive.org/JMeter-User-f512775.html --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
