Fortinet Document Library

Version:


Table of Contents

User Guide

21.4.0
Copy Link

Specifying confirmation check locations

Whenever a service has an outage, we perform several test checks from different locations to ensure that it is not a false positive. You can choose which monitoring locations you would like to perform these confirmation checks from through a feature we call whitelist. This feature can be very useful for a number of reasons. Say, for example, you would only like your confirmation checks to come from monitoring nodes very close to your primary monitoring location, which would allow you to keep track of local network outages. Additionally, If you are explicitly opening firewall rules for a service to be checked, this allows you to keep that list controlled and manageable despite how many new nodes we add.

To create a whitelist, perform the following steps:

  1. Go to the server’s Instance Details page. 

  2. Under the Details tab, select Monitoring Location.

    The Monitoring Configuration drawers slides out.

  3. Enable Whitelist locations.

    Your confirmation node should be set to default. From here you can select to use either a whitelist. A whitelist will let you make a list of all of the monitoring locations you would like to include. Deselecting a location will exclude the location. When you enable Whitelist locations, you will see a list of all of our monitoring nodes to either include or exclude. You will need to leave at least seven monitoring nodes to run these confirmations checks, which is the minimum number required by our algorithms.

  4. Once you have selected all of the monitoring nodes you would like, click Save Changes to save this configuration. From now on all confirmation checks for this server will be restricted according to your configuration.

Specifying confirmation check locations

Whenever a service has an outage, we perform several test checks from different locations to ensure that it is not a false positive. You can choose which monitoring locations you would like to perform these confirmation checks from through a feature we call whitelist. This feature can be very useful for a number of reasons. Say, for example, you would only like your confirmation checks to come from monitoring nodes very close to your primary monitoring location, which would allow you to keep track of local network outages. Additionally, If you are explicitly opening firewall rules for a service to be checked, this allows you to keep that list controlled and manageable despite how many new nodes we add.

To create a whitelist, perform the following steps:

  1. Go to the server’s Instance Details page. 

  2. Under the Details tab, select Monitoring Location.

    The Monitoring Configuration drawers slides out.

  3. Enable Whitelist locations.

    Your confirmation node should be set to default. From here you can select to use either a whitelist. A whitelist will let you make a list of all of the monitoring locations you would like to include. Deselecting a location will exclude the location. When you enable Whitelist locations, you will see a list of all of our monitoring nodes to either include or exclude. You will need to leave at least seven monitoring nodes to run these confirmations checks, which is the minimum number required by our algorithms.

  4. Once you have selected all of the monitoring nodes you would like, click Save Changes to save this configuration. From now on all confirmation checks for this server will be restricted according to your configuration.