Manage SolarWinds Observability Agents
Most Agent management activities are performed on the Agents settings page.
- Access Agents
- Update deployed Agents
- Update deployed Agents
- Start, stop, or restart plugins
- Rename an Agent
- Remove host monitoring from an Agent
- Delete Agents
- Restart the Agent in SolarWinds Observability SaaS
- Enable host monitoring on an Agent
The following Agent management activities require accessing the machine where the Agent is deployed.
Start, stop, restart, or check the status of Agents on the machine
On a Windows machine, go to Services, select the SolarWinds UAMS Client and execute start, stop, or restart.
You can also use the following commands, based on the operating system of the machine:
Windows
Run the following PowerShell scripts to start, stop, restart, or get information on the client status
Start-Service swiuamsclientd
Stop-Service swiuamsclientd
Restart-Service swiuamsclientd
Get-Service swiuamsclientd Linux
sudo systemctl start uamsclient.service
sudo systemctl stop uamsclient.service
sudo systemctl restart uamsclient.service
sudo systemctl status uamsclient.service CentOS 6
sudo service uamsclient start
sudo service uamsclient stop
sudo service uamsclient restart
sudo service uamsclient status Configure proxy for SolarWinds Observability Agents
You can set up proxy for the Agent by using the global environment variable HTTPS_PROXY. The variable is natively supported by the gprc library. For details, see Proxy in the grpc repository in GitHub.
Environment variable
HTTPS_PROXY
Description
Optional configuration. This option can be used to connect through a proxy. It can be set through the environment variable HTTPS_PROXY. See Windows-based Agents or Linux-based Agents.
Valid values
IP Address:Port
Windows-based Agents
To set up the proxy on Windows, add a new system environment variable in System Properties. The Variable name should be HTTPS_PROXY and the variable value should be the proxy's IP address and port, with the format of IP Address:Port.
Configure the proxy only for a Windows Agent
To set up the proxy only for the Agent, run the following commands:
-
Set up the proxy.
C:\'Program Files'\SolarWinds\UAMSClient\uamsclient-ctl.exe set-proxy -proxy "IP Address:Port" -work-dir $env:programData\SolarWinds\UAMSClient -log-dir $env:programData\SolarWinds\UAMSClient\log -
Restart the Agent service:
Restart-Service swiuamsclientd
Linux-based Agents
To set up the proxy on Linux, define the HTTPS_PROXY="IP Address:port" environmental variable in the /etc/environment file. When the variable is set, restart the Agent service.
Configure the proxy only for a Linux Agent
To set up the proxy only for the Agent, run the following commands:
-
Set up the proxy.
sudo -u swagent /opt/solarwinds/uamsclient/sbin/uamsclient-ctl set-proxy -proxy "IP Address:port" -work-dir /opt/solarwinds/uamsclient/etc -log-dir /var/log/solarwinds/uamsclient -
Restart the Agent service:
sudo systemctl restart uamsclient.service
Update the API token for an Agent already installed on a host
To change the token used for installing an Agent on a host, you can either re-install the Agent using the new token, or manually execute a command on the target host.
Use the command for the operating system on the host.
Replace <YOUR_TOKEN> with the new token from SolarWinds Observability SaaS.
Windows
C:\'Program Files'\SolarWinds\UAMSClient\uamsclient-ctl.exe set-access-token -work-dir $env:programData\SolarWinds\UAMSClient -log-dir $env:programData\SolarWinds\UAMSClient\log --token <YOUR_TOKEN> Linux
sudo -u swagent /opt/solarwinds/uamsclient/sbin/uamsclient-ctl set-access-token -work-dir /opt/solarwinds/uamsclient/etc -log-dir /var/log/solarwinds/uamsclient --token <YOUR_TOKEN>