On-Premise Load Agents
- On the controller, in the Other Options -> Load Agents section of the Workflow Tree, the grid displays agents attached to the controller.
- The first agent, called Local is the controller by itself.
- To attach a new agent, on the grid’s toolbar, click Connect Load Agent.
Enter required connection properties: Agent Name, Load agent OS (Windows or Linux), Hostname or IP address without "//", Port, Username, and Password.
Starting from v5.6, the password will be encrypted in the configuration file (.ssconfig)
Click Test Connection. If a pop-up message indicates any connectivity issues, correct them and try again.
If the connection is successful, the connection latency will be displayed
- If the message indicates that the connection is successfully verified, click Add Agent.
- A new agent will appear in on the list.
- To edit the existing connection, selected select it on the grid and click Edit Selected Load Agent Connection on the toolbar. Alternatively, you can right-click and select Edit, or double-click on the agent’s name.
- To delete the existing connection, selected select it in the grid and click Delete Selected Load Agent Connection on the toolbar. Alternatively, you can right-click and select Delete.
|Note: To communicate with the controller, the Agent has a listener on TCP port 49998 (or another port if you changed the default port while Configuring Agent) If the Controller displays a communication error, make sure that StresStimulus is running on the remote computer in agent mode, and that TCP port 49998 is opened on firewalls between the controller and agents.
Cloud Load AgentsTo create a cloud load agent on the fly, click Create Cloud Load Agent. Then refer to Creating AWS EC2 Agents for AWS or Creating Azure Agents for Azure.
Distributed test runtime
The connection between the Controller and every load agent must be maintained throughout the duration of the distributed test. During every graph sample rate interval, the Controller polls every load agent for progress data and then combines the data to update the overall test progress. The Controller will continue polling each load agent until every load agent reaches the test completion criteria. When each load agent has reached its test completion criteria, the Controller will start to calculate the overall test results.
Stopping a distributed test
When the user manually stops a distributed test, the Controller sends a signal to the agent to stop the test. The overall test will stop when all load agents have stopped the test. If the connection between the Controller and any load agent is disrupted (or if the load agent crashes) for an extended period of time, the Controller automatically stops the test.
If, during the test, the Controller loses connection (or crashes) with the load agent, the load agent will stop the test automatically after a short time.