[-]
  
  
[-]
  
  
  
  
  
  
  
 
 
[-]
  
  
  
  
[-]
  
 [+]
  
[-]
Monitoring
  
 [+]
 [+]
 [+]
  
[-]
Monitoring guides
  
  
[-]
Templates
  
  
  
[-]
Cloud monitoring
 [+]
  
  
 [+]
Kubernetes
[-]
Network checks
 [+]
  
  
  
[-]
 [+]
  
  
  
  
  
  
 [+]
 [+]
 [+]
 [+]
[-]
CounterMeasures
  
 [+]
 [+]
  
  
[-]
Panopta OnSight
 [+]
 [+]
[-]
SNMP
 [+]
  
[-]
Alerting
 [+]
 [+]
 [+]
 [+]
 [+]
[-]
Reporting
  
  
  
[-]
Maintenance
  
  
[-]
API
  
  
  
  
[-]
Users, Groups, and Authentication
 [+]
  
  
  
[-]
Billing and Payments
  
  
  
  
  
  
 
[-]
  
  
  
  
  
  
  
  
  
  
  
  
Updated on 7/26/2019
Online Help
IP matching
Direct link to topic in this publication:

The Panopta Server Agent has default IP matching which fires during the initial handshake. This IP matching can be helpful or the following scenarios:
  • If a user may have uninstalled the agent and is looking to reinstall. Rather than creating a new entry/object, we would want to attach the Agent to the same server as before to avoid duplication and keep all historical data. This works by the Agent sending the IP addresses of the instance to our cloud, and then we check to see if those IP's exist in your account. If they do, we automatically attach the Agent back to that particular server.
  • For users moving on from basic instances (without the agent) to advanced instances. In this case, instead of the Agent setting up a new Instance (duplicating the existing instance), the IP matching would step in and assign the Agent to the server with the matching IP.

However, this can backfire in cases with multiple networks and overlapping IP ranges. If you happen to have the same IP in separate networks monitored by Panopta, we've given you the ability to disable this IP matching. The option is called disable_server_match and is further documented here.