While NS1 is primarily used for DNS and traffic management, we also have a robust monitoring solution built right into our portal. Monitoring can be used as a standalone service for alerts, or as a Data Feed for real-time traffic management. Monitoring via Ping (ICMP) or TCP can be done in just a few simple steps.
This article focuses on how you can set up monitoring for HTTP or HTTPS servers using a TCP job.
- Click the Monitors tab, and then click the Add Monitor button.
- Configure options on the new monitoring job—such as job type, regions to monitor from, and frequency of checks. Note: If you are monitoring an HTTP server, set the TCP port to 80. For an HTTPS server, set the TCP port to 443. Note: SSL negotiation takes place during the "connection" phase, and can affect Connect Timeout. Monitors should be configured appropriately if using SSL.
- Provide additional changes—such as toggling advanced options or including a string to send.
- Click the Notifications tab, and either attach an existing notification list or create a new one.
- Your new monitoring job is running and will keep you informed of any uptime changes.
Now, you can connect this new monitor to an answer for a Filter Chain record.
- Navigate to the record, and click the plug icon in the Up metadata row.
- Select NS1 Monitors from the menu, and choose your new monitor.
- Click Save.