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 offers.
- 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
- You're deploying the OnSight in an AWS environment
- You're looking for the simplest cloud deployment method
- 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
Looking to automate OnSight deployment?
If you're looking to automate the deployment of new OnSight vCollectors, follow the instructions listed here
It is imperative that a few ports in your firewall are open for for the OnSight's outbound connectivity according to the table below.
aggregator2-secondary.panopta.com (regional failover)
80/tcp, 443/tcp, 22/tcp
The first is for standard communication with Panopta servers, the second and third are required for initial installation, and future upgrades and updates.