The “failover after” setting (shown below) in the main Failover Pool configuration is the number of our cloud nodes (datacenters) that must see your server as DOWN before actually failing over. All of our datacenters monitor your servers all the time. This setting simply allows you to increase the reliability of the results before action […]
How often can I configure a monitor to test my server, and what parameters are available for testing and determining if it is down?
You can configure any monitor to test your server(s) as often as once per minute (the test “Interval”). Additionally, you can configure these parameters: Response Time-out (in seconds) – This is how long the monitor will wait for a particular test to come back positive or negative. Down Time (in seconds) – This is a […]
The DNS Failover Service determines a server is down based on the monitoring type you’ve selected and configured. For example, if you’ve created a PING monitor and assigned that to your server, as soon as it stops pinging and exceeds the test “interval” and “retries” values you’ve specified, it will be considered “down” and subject […]
How can I reliably monitor my database server to see if it is online, or in the case of a replicated database, if it is the primary or not?
The recommended way to monitor any type of database, including Microsoft SQL Server, is to create a hidden web-page that does a specific database query, and when successfully completed, sends a word (e.g. “OK”) to the web browser. This method is secure because you need not open SQL ports in your firewall to allow our […]
Yes, absolutely. When creating an HTTP monitor, you can go to the SPECIAL PARAMETERS tab and adjust the HTTP Request value to look for your special page. By default the HTTP Request value is “HEAD /”. If, for example, you wanted to test the page at https://www.mydomain.com/test.php, you would change the value in the HTTP Request […]
Yes, absolutely. This is a very common use for our DNS Failover service. While some customers use it to switch between servers at different datacenters, it works very well to switch between the same server that has two different public IP addresses at the same location or datacenter (e.g. two ISPs, two WAN connections etc.) DNS […]
We support the following list of response codes which can be used individually or together to determine the state of a server. 100 – Continue 101 – Switching Protocols 200 – OK 201 – Created 202 – Accepted 203 – Authoritative Information 204 – No Content 205 – Reset Content 206 – Partial Content 300 […]
MONITORS OVERVIEW The Cloud Networking system supports a very large subset of monitors from something as simple as a ping to something more complex as a DNS record lookup or even an HTTP Post that looks for specific content on the return. Configuring the correct monitor is essential to properly detecting outages for devices. Below […]