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.
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:
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 servers 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:
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.
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.
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 Agent installation.
The following list provides the minimum Linux VM requirements for a standalone Onsight vCollector deployment:
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 t3.medium instance - as your monitoring expands, we recommend 1 core + 1 GB Ram per 1,000 checks
A virtual image of the OnSight vCollector is available if you want to deploy it to your hypervisor. For a detailed procedure, see OnSight virtual image installation.
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:
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.
To grant Panopta access to Cloudwatch, see AWS monitoring
To grant Panopta access to Azure, see Azure monitoring
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:
Ensure you are logged in to the Panopta control panel at my.panopta.com.
From the main navigation header, click Add.
In the modal that appears, locate the Website/Endpoint card then click Select.
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.
You can add your infrastructure to Panopta via Panopta’s API. For more information, see the following topics: