- This line was added.
- This line was removed.
- Formatting was changed.
The OnSight vCollector is a lightweight appliance that functions similarly to our public monitoring nodes, which runs uptime checks and synthetic monitoring against your publicly available servers and web endpoints. However, the OnSight vCollector sits within your private network and monitors resources that are not publicly exposed. The OnSight can run uptime and synthetic checks on your private infrastructure, monitoring things like RDP, database connectivity, and port availability.
The OnSight can also function as a proxy for servers that have the Server Agent installed but have no outbound connectivity. Also, the OnSight can monitor network devices, storage arrays, VMWare clusters, and private network-managed cloud resources such as RDS and DynamoDB.
The OnSight is a collection of Docker containers that provide the necessary services. During the installation of the OnSight, if Docker is not found on the target machine it will automatically be installed.
The OnSight vCollector supports the following Linux distributions:
Debian 9 and 10
Ubuntu Server 16.04 LTS, 18.04 LTS, and 20.04 LTS
Redhat Enterprise 7.x and 8-8.3
CentOS 7.x and 8-8.2
Oracle Enterprise Linux 7.0
Amazon Linux 2 and 2018.03
Please note that podman should not be installed already on the OS. We utilize only Docker currently. Our installation process will install it if it's not found.
The docker SNAP package requires additional configuration that may be environment dependent. We currently only support the docker.io package installation. If the SNAP version was installed during installtion, you should remove it and install the docker.io package using your package manager.
These are the minimum resources required to install the OnSight.
Processor: 4 cores
Memory: 8 GB
Hard disk space: 50 GB
For larger deployments involving a significant number of network devices or advanced synthetic checks, please contact our support team to help determine the resource requirements for your environment.
Network connectivity requirements
The host machine must have outbound access to the following:
Primary and fail-over communication with the Panopta cloud
OnSight software updates
OnSight software updates
Docker download and installation
The host machine must have inbound access to the following ports allowed:
Used to SSH into host
Used to configure the OnSight as a proxy for agents
Used for SNMP Trap receipt
Used for NCM console
You're comfortable operating in a Linux environment
You're deploying the OnSight in an AWS environment
You prefer a "black box" deployment
On this page
|Table of Contents|