You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you're prompted for a passphrase, your key is protected with one. ATP doesn't support SSH keys with passphrases, so you need to create a separate key without a passphrase for ATP.
192
187
193
-
###Create a passphrase-free key for ATP (if needed)
188
+
## Create a passphrase-free key for ATP (if needed)
194
189
195
190
If your existing SSH key has a passphrase, generate a new key specifically for ATP:
196
191
@@ -212,9 +207,9 @@ If your existing key is in the default location (`~/.ssh/id_ed25519` or `~/.ssh/
You can now use `~/.ssh/atp_key` as the private key when configuring ATP's target connection.
210
+
You can now use `~/.ssh/atp_key` as the private key when configuring the ATP target connection.
216
211
217
-
###Enable passwordless sudo on the target
212
+
## Enable passwordless sudo on the target
218
213
219
214
ATP needs to run commands with elevated privileges on the target system. Because ATP cannot enter sudo passwords interactively, configure passwordless sudo access.
220
215
@@ -238,7 +233,7 @@ After installing ATP and preparing your target, you can connect using either the
238
233
239
234
### Connect using the ATP GUI
240
235
241
-
The GUI is typically used on Windows and macOS hosts, though it's also available on Linux.
236
+
Use the GUI on Windows and macOS hosts, though you can also run it on Linux.
242
237
243
238
Open the ATP application.
244
239
@@ -248,24 +243,25 @@ Select **Add Target**.
248
243
249
244
In the **Configure Target** form, provide the following details:
250
245
251
-
***Host**: The hostname or IP address of the target machine
252
-
***Name**: A descriptive name for the target
253
-
***Port**: The SSH port number (default is 22)
254
-
***User**: The username for SSH connection
255
-
***SSH Private Key**: Choose**Automatically Detect Key** or **Select Key Manually**
246
+
***Host**: the hostname or IP address of the target machine
247
+
***Name**: a descriptive name for the target
248
+
***Port**: the SSH port number (default is 22)
249
+
***User**: the username for SSH connection
250
+
***SSH Private Key**: choose**Automatically Detect Key** or **Select Key Manually**
256
251
* For manual selection, enter the path to your private key (usually `~/.ssh/id_rsa` or `~/.ssh/id_ed25519`)
257
252
***Host Key Verification**: Choose **Strict** (recommended) or **Ignore**
258
253
* Strict mode verifies the server identity using your `~/.ssh/known_hosts` file
259
254
260
-

255
+

256
+
261
257
262
258
Select **Add Target**.
263
259
264
260
The target appears in the targets list and is ready for profiling.
265
261
266
262
You can select the **Test Connection** button to verify your connection to the ATP Linux target is successful.
267
263
268
-

264
+

269
265
270
266
#### Configure jump nodes (optional)
271
267
@@ -310,7 +306,7 @@ atperf --help
310
306
311
307
If your target is the same machine where you installed ATP (the host machine itself), ATP automatically provides a built-in `localhost` target. You don't need to configure authentication, SSH keys, or host verification for local profiling.
312
308
313
-
Verify the localhost target is available:
309
+
Verify the localhost target is available by listing all configured targets:
314
310
315
311
```bash
316
312
atperf target list
@@ -328,7 +324,7 @@ Your local machine is now ready to use as a target. Specify `--target=localhost`
328
324
329
325
#### Add a remote target
330
326
331
-
To profile a workload on a remote machine, add it as a target using the standard syntax:
327
+
To profile a workload on a remote machine, add it as a target using the standard syntax. This command registers the remote system with ATP:
0 commit comments