Using a Cloud Collector
We can provide additional Collectors for you within your dedicated environment. This will incur extra cost on your plan.
Using Your Own Collectors
You can use your own Opsview Cloud Collectors hosted within your own networks that communicate with your Opsview Cloud system for monitoring hosts locally. These Collectors can be set up individually or in a group that work together and share load (a Collector Cluster).
The installation of the required packages and setup is completed by Customer Success.
You need to fulfil these requirements to allow Customer Success to install the required packages and configuration files on each Collector you want to set up
- Provide a name for this new Collector or Collector Cluster
- Provide a user with a known password OR SSH key (where you can provide the public key to Customer Success); this user must have full SUDO access
- Python 3 installed
- Firewall rules allowing either:
- incoming port 22/TCP from your Opsview Cloud server IP address, where connections are initiated by your Opsview Cloud server (Reverse SSH tunnel), OR
- outgoing port 22/TCP Opsview Cloud server IP address, where connections are initiated by your onsite Collector (Forward SSH tunnel)
- When you have your server set up on a supported OS from the table below you can then create a support ticket to get the collector set up.
Support Operating Systems
|DISTRIBUTION|RELEASE|ARCHITECTURE|STATUS| | – | – | – | |Debian|8 (Jessie)|64-bit| |CentOS|7|64-bit | |RHEL|7 |64-bit | |OL (Formally known as OEL)|7 |64-bit | |Ubuntu (LTS) |16.04 (Xenial) |64-bit | |Ubuntu (LTS)|18.04 (Bionic Beaver) |64-bit |
Reverse SSH Tunnel
The Reverse SSH Tunnel connection is initiated and maintained by the Opsview Cloud Orchestrator to your new Collector on port 22/TCP (or other defined ported). After verifying the connection details (and user access SUDO rights), Customer Success will be able to add in the required configuration onto the Orchestrator, install the additional packages and configuration on the new Collector and then bring into use. At this point you will be able to assign Hosts to be monitored to the Collector (or Collector Cluster) by setting the ‘Monitored By’ to your new cluster in the Advanced section on the Host Edit page.
Forward SSH Tunnel
The Forward SSH Tunnel connection is initiated and maintained by each of your new Collectors to the Opsview Cloud Orchestrator on port 22/tcp.
The process is:
- Create a new user (in this example,
opsiewsupport) on the server, using a command similar to:
useradd -m -s /bin/bash opsviewsupport
- Ensure the user has full sudo access by running
visudoand adding the following line into the file:
opsviewsupport ALL=(ALL) NOPASSWD:ALL
- Switch to the new user and make a new ssh key using the following command:
su - opsviewsupport ssh-keygen -o -a 100 -t ed25519 -f $HOME/.ssh/id_ed25519 -N '' -C "Created on $(date) for Opsview Support access"
- As this user, download your unique public key from your cloud server and set the right permissions on it:
curl -o $HOME/.ssh/authorized_keys https://$YOUR_CLOUD_SERVER.cloud.opsview.com/authorized_keys chmod 0600 $HOME/.ssh/authorized_keys
- Provide Opsview Support with your generated public key, the username of the account you have created (‘opsviewsupport’ in this instance) and IP address information for the Collector:
id ip a curl ifconfig.me cat $HOME/.ssh/id_ed25519.pub
After Customer Success has added your public key onto your cloud server, you should be able to open an SSH tunnel using the following command:
# Use a different `$ORCHESTRATOR_PORT` for each of your collectors from within the range 9020 to 9900 ssh -N -R $ORCHESTRATOR_PORT:localhost:22 -l $YOUR_CLOUD_ADMIN_USER $YOUR_CLOUD_SERVER.cloud.opsview.com
Customer Success will then configure the Collector in your cloud system system and start the setup process. After the setup is complete, you will be able to assign Hosts to be monitored to the Collector (or Collector Cluster) by setting the ‘Monitored By’ in the Advanced section on the Host Edit page to your new Cluster .