Adding Collectors

How to add a Collector to your environment

If you need to add more capacity in your Opsview Cloud system by adding a new Collector; you will need to create a request in our Support Portal .

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.

Requirements

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 2.7 installed and available as /usr/bin/python
  • 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

DISTRIBUTIONRELEASEARCHITECTURE
Debian8 (Jessie)64-bit
Debian10 (Buster)64-bit
CentOS764-bit
RHEL764-bit
RHEL864-bit
OL (Formally known as OEL)764-bit
Ubuntu (LTS)18.04 (Bionic Beaver)64-bit
Ubuntu (LTS)20.04 (Focal Fossa)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.

To set up this type of connection you must create an SSH keypair and provide the public key file to Customer Success. initiate an SSH session with credentials provided by Customer Success using the following command:

# Use a different ORCHESTRATOR_PORT per collector from within the range 9020 to 9900
ssh -R<Orchestrator_port>:localhost:22 -l <username> <IP_of_your_Orchestrator>

This will then allow Customer Success to connect to your server and verify the connection (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.