Start Monitoring Physical Servers Using the Telegraf Deployment Script on a Linux Platform

You can use a sample script to monitor operating systems in physical servers.

The sample script is tested only on the following operating systems:

CentOS 7.x and CentOS 8.x
RHEL 7.x and RHEL 8.x
SUSE 12.x and SUSE 15.x
OEL7.x and OEL 8.x
Ubuntu 16.x, Ubuntu 18.x, Ubuntu 20.x, and Ubuntu 22.x
VMware Photon Linux

Prerequisites

Verify that cURL is at 7.29.0.
Verify that unzip is at 6.0-20.el7 or above.
Verify that OpenSSL is at 1.0.2k-fips or above.
Ensure that cloud proxy is up and online in vRealize Operations.
Ensure that cloud proxy is reachable from the physical server.
Ensure that port 443 of vRealize Operations is reachable from the physical server.
The uuidgen package must exist on the physical server.

Note: If you have already used custom Telegraf and have upgraded vRealize Operations, and you want to view the new properties of the operating system objects, you must reperform the following steps to monitor operating systems. You must download the helper script again, rerun it, then restart custom Telegraf.

Procedure

SSH to the physical server and download the sample script from cloud proxy by running the following command:
```
wget --no-check-certificate https://<cloudproxy_ip>/downloads/salt/unmanagedagent_setup_sample.sh 
```
Note: Use the relevant cloud proxy IP address for <cloudproxy_ip> in the preceding location specified.
Make the script executable by running the following command:
```
chmod +x unmanagedagent_setup_sample.sh
```
Run the sample script to download the Telegraf binary files from cloud proxy, create necessary certificates for a secure connection with vRealize Operations, and make necessary updates in Telegraf configuration files:
```
./unmanagedagent_setup_sample.sh -v <vrops_ip_or_fqdn> -a <vrops_user> -b <vrops_password> -c <cloudproxy_ip> -d <Telegraf_Download_Directory> 

Example: 
./unmanagedagent_setup_sample.sh -v 10.192.0.189 -a admin -b Password!23 -c 10.192.0.158 -d /opt/TelegrafDownloadDirectory 
```
If the environment is behind a corporate proxy, the script considers the proxy explicitly for external connections.
Note: Ensure that the special characters in the user name and password are either encoded or escaped correctly for proxy authentication:
```
./unmanagedagent_setup_sample.sh -v <vrops_ip_or_fqdn> -a <vrops_user> -b <vrops_password> -c <cloudproxy_ip> -d <Telegraf_Download_Directory> -x <[protocol://]proxyhost[:proxyport]> -u <proxyUser> -p <proxyPassword>
```
Description of arguments:
vrops_ip_or_fqdn: IP or FQDN of vRealize Operations. Mandatory parameter.

vrops_user: User name of vRealize Operations to make a suite-api call. Mandatory parameter.

vrops_password: Password of vRealize Operations to make a suite-api call. Mandatory parameter.

cloudproxy_ip: IP of Cloud Proxy. Mandatory parameter.

Telegraf_Download_Directory: Where to install the agent? It's an optional parameter. Default value: current directory.

proxy: Proxy Server URL. Optional parameter.

Note: If helper script execution fails for the first time due to wrong arguments, clear the Telegraf folder and rerun the script once more with the right arguments.

cd the <Telegraf_Download_Directory> folder and run Telegraf.

telegraf/usr/bin/telegraf -config telegraf/etc/telegraf/telegraf.conf -config-directory telegraf/etc/telegraf/telegraf.d

What to do next

You can view metrics by selecting the relevant object > Metrics tab from the vRealize Operations user interface.

From the left panel, navigate to Environment > Custom Groups.
Click the Operating System World object in the right pane.
Navigate to the Metrics tab and select the corresponding OS object.