The OnSight vCollector functions the same as one of our public monitoring nodes, running uptime checks and synthetic monitoring against your publicly available servers and web endpoints. However, the OnSight vCollector sits behind your firewall and monitors your private network. The OnSight can run uptime and synthetic checks on your servers behind the firewall, 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 connection to the outside Internet. As well, the OnSight can also monitor network devices with SNMP.

You don’t need to use OnSight to use the Agent or vice versa, but using both gives you a more full view of your infrastructure with the different kinds of monitoring each offer.

Deployment methods

Installation Method Best for
Standalone installer You're comfortable operating in a Linux environment
You have a specific server image you want to conform to
You have an available Linux VM
AWS AMI You're deploying the OnSight in an AWS environment
You're looking for the simplest cloud deployment method
Virtual image You prefer a "black box" deployment
You have the available resources to allocate to a VM
You'd like to deploy on the HyperVisor of your choosing
Docker container

You prefer to install the Docker version of the OnSight vCollector

The Docker container for the OnSight is available here

Looking to automate OnSight deployment?

If you're looking to automate the deployment of new OnSight vCollectors, follow the instructions listed here.

Connectivity details

It is imperative that a few ports in your firewall are open for the OnSight's outbound connectivity according to the table below.

Used for 
443/tcp (regional failover)         

Standard communication with Panopta servers 
80/tcp, 443/tcp, 22/tcp
Initial installation 
80/tcp, 443/tcp
Initial installation 
Reserved for future updates and upgrades