This article describes the methods you can use to add your infrastructure to Panopta. Each method varies in effort, requirements, and level of automation. Review the different deployment methods listed in this article to determine which option works best for your environment.

Refer to the following table to see the features and requirements of each option. Click on each of the feature's headings in the following table for a short description of the feature or requirement. 

Features Requirements
External monitoring

Ability to monitor local instances and instances from Panopta's public nodes, such as HTTP, Ping, Multi-step checks, etc.

Server metrics
Metrics obtained via the Panopta Agent, such as CPU, disk, memory, application metrics, etc.

Metrics obtained from network devices using OnSight.


Automated actions to incidents triggered on your infrastructure.

See also

Auto-discover instances

This method can auto-discover and add new instances once initial configuration is complete. 

Instance access

Direct access to the instance is required to utilize this method.

Network access

Your network will be scanned for devices. This may trigger security warnings.

Panopta Agent

OnSight Discovery

Panopta Cloud Discovery

OnSight vCollector installer


Add a basic instance

Add via API

For example, if you want to use CounterMeasures, add your infrastructure using the Panopta Agent method. Otherwise, if you only want to monitor SNMP-related metrics, add your infrastructure manually or use OnSight Discovery.

Click on the following links to learn more about each deployment method:

Panopta Agent

The Panopta Agent is a local monitoring utility that is deployed directly on your physical server, VM, or cloud server. It allows you to monitor your server’s resources, processes, and services. The Panopta Agent also supports several plugins to monitor applications like web servers, databases, caches, and so forth. It is also extensible, allowing you to customize it to meet your own needs. 

The Panopta Agent can be used to monitor applications running on your server such as Apache, Cassandra, SQL Server, and more . The Agent is compatible with Windows, Linux, and Unix.

Click on the following links to learn more about the Panopta Agent:

OnSight vCollector installer

The Onsight vCollector sits behind your firewall or within your virtual private cloud. It can perform network checks, SNMP polling, and serve as a proxy for Panopta Agents. It can also be used to provide deeper monitoring on network devices such as switches, routers, and firewalls.

Panopta enables you to synthetically monitor servers, web endpoints and other network based services from behind your firewall with an OnSight vCollector or Panopta Public Monitoring Probes . These checks provide deeper insight into your applications beyond just basic uptime.

See also:

The Onsight vCollector can be installed on a Linux VM, as an AMI in an AWS environment, as a Virtual Machine in Azure, or on any other hypervisor you are using. Docker images are also available for container-based environments.

Once deployed, an OnSight vCollector can scan your network or private cloud for instances and devices using a specified CIDR range. The discovered instances and devices can be added automatically or manually. Instances and devices discovered by the OnSight can be found under the Discovered Instances tab of your OnSight's details page.

OnSight Automation

You can deploy an OnSight vCollector instance to a Linux VM by following the instructions provided in the OnSight standalone installer. You can also automate the deployment of OnSight vCollectors by following the instructions provided in Automate the Panopta OnSight deployment.

The following list provides the minimum Linux VM requirements for a standalone Onsight vCollector deployment:

  • Ubuntu LTS (from 16.04 to 18.04) or RHEL/CentOS 7.x( or newer)
  • Python 2.7x
  • At least 2 CPU cores
  • At least 4 GB of memory
  • 30 GB of available hard disk space 
  • Root access with the ability to create users and install system packages
Information     Note: As your monitoring expands, we recommend 1 core + 1 GB Ram per 1,000 checks.


If you are deploying the OnSight vCollector as an AMI in your AWS environment, follow the procedures in Install Panopta OnSight to an AWS instance.
The following list provides the minimum requirements for an AWS AMI OnSight vCollector deployment:

  • Minimum of a t1.micro instance - as your monitoring expands, we recommend 1 core + 1 GB Ram per 1,000 checks
  • See the following table for connectivity requirements:

Connectivity requirements

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 

Virtual image

A virtual image of the OnSight vCollector is available if you want to deploy to your hypervisor. For a detailed procedure, see OnSight virtual image installation.

OnSight Discovery

Once you've installed the OnSight vCollector, you can use it to discover your infrastructure. The OnSight discovery tool allows you to scan your infrastructure and automatically add devices to your Panopta account. After installing the OnSight, you can customize how the tool searches for new devices. You can define an IP range, the re-scan frequency, and the scan type to determine precisely what devices should be added. Servers and devices discovered by OnSight can be found under the Discovered Instances tab on the OnSight page.

Click on the following link to learn more about the OnSight Discovery tool:

Panopta Cloud Discovery

OnSight Cloud Discovery allows you to scan your infrastructure from different cloud platforms (AWS or Azure). Data gathered from these cloud platforms should be used as an augmentation of, not a replacement for, the data obtained by the Panopta server agent and external monitoring. The server agent can provide more detailed and accurate data across any OS distribution or application you may be running on your compute instance. Also, Panopta’s external monitoring ensures you're getting the full picture of your current operating environment as well as a view into what your customers are experiencing.

Add a basic instance

Manually adding an instance allows you to monitor publicly available websites, endpoints, servers, services, and more via FQDN or IP. To add a basic instance, perform the following steps:

  1. Ensure you are logged in to the Panopta control panel at
  2. From the main navigation header, click + Add.
  3. In the modal that appears, click Instance - Manual.

You are now in the add instance flow. From here, you can configure details about your instance and how you'd like to monitor it. 

If you want to monitor instances that are not publicly accessible, add your instances using the Onsight vCollector method

Add via API

You can add your infrastructure to Panopta via Panopta’s API. For more information, see the following topics: