Skip to content

Frequently Asked Questions

Resource Management

A: Yes, resource requirements scale with traffic volume. While the basic configuration (1 vCPU, 2GB RAM) is sufficient for initial deployment, you should monitor usage and scale resources based on:

  • Number of concurrent scans
  • Volume of scan requests
  • Integration complexity
  • Network latency

Monitor your Private Location's performance through logging and monitoring and contact our support team if you need assistance with scaling.

Availability & Connectivity

Q: Does the Private Location restart automatically if it disconnects?

A: Yes, the Private Location includes automatic restart capabilities. When deployed using Docker Compose or Helm with the restart: always policy, the service will automatically restart if it becomes disconnected or encounters issues.

Q: Does the Private Location turn off after a certain amount of time or lack of connections from Escape?

A: No, the Private Location remains active as long as it maintains connectivity to the Escape platform. The service continuously pings the Escape platform at regular intervals (approximately every second) to maintain its connection status and availability for scan requests.

Health Monitoring

Q: How does Escape determine if a Private Location is alive and operational?

A: Escape monitors Private Location health through continuous heartbeat mechanisms:

  • Regular Pings: The Private Location sends periodic health checks to the Escape platform (approximately every second)
  • Connection Status: The platform tracks the connection status and availability of each Private Location
  • Response Monitoring: Escape monitors response times and success rates of scan requests

You can monitor your Private Location's health and performance through the Escape platform's Private Locations page and implement additional monitoring using the logging and monitoring capabilities.

Troubleshooting

If you experience connectivity issues or need to troubleshoot your Private Location:

  1. Check the deployment configuration and ensure your API key is correctly set
  2. Verify firewall settings allow the necessary outbound connections
  3. Review SSL/TLS configuration if using secure connections
  4. Monitor logs using the logging and monitoring tools
  5. Contact our support team for assistance with persistent issues