Adding a Machine

You can turn a Linux or Windows machine into a load generator. The machine needs to reach Atlas over HTTPS on the way out; Atlas never needs to reach in.

Who can do this

Adding machines is an administrator action. If Fleet isn't in your sidebar, ask your administrator.

What the machine needs

• Linux (Ubuntu or Debian) or Windows
• Enough memory to be worth using — 8 GB is a sensible floor, 16 GB is comfortable. JMeter is memory-hungry and an undersized machine will fail to start rather than run slowly.
• Outbound HTTPS to your Atlas instance
• Network access to whatever you intend to load test

Java and JMeter are installed for you.

Adding one

Go to Fleet → Add and choose Linux load generator or Windows load generator. Pick a pool, and Atlas gives you a one-line command.

Run that command on the machine. It installs Java, JMeter and the Atlas agent, registers the machine, and starts it.

The dialog watches for the machine to connect and shows Connected ✓ when it does — usually a few seconds after the installer finishes. The machine then appears in the Fleet list, named after its hostname.

Treat the command as a secret

The command contains an enrolment token. Anyone who has it can register a machine into your account. Don't paste it into a ticket or a chat channel.

Connection types

Most machines use the agent: it dials out to Atlas and holds the connection open, so nothing needs to be exposed inbound. This is the right choice almost always, and the only choice on Windows.

Direct SSH is offered for Linux machines that Atlas can reach directly. It gives you live per-machine statistics in Watch, which the agent doesn't currently provide. Choose it only when the machine is reachable and you want that.

Checking it worked

The machine appears under Fleet → Servers with its connection shown as live. Run a small test against it to confirm end to end — a single generator, a short plan — before including it in a real run.

Removing one

Delete it from the Fleet page. On the machine itself, stop and disable the Atlas agent service to stop it reconnecting.