When a monitor uses 'Global Verify' as a monitoring type, a remote test is performed at a different location to verify an error before a notification is triggered. The location selected for remote verification is not random, it is selected based on specific rules. Each location has its own predefined Primary and Secondary Location it uses for Remote Verification if possible. The locations selected on the account and for the monitor itself are considered in determining which location to use.
When a monitor needs to trigger a test from a remote location, it follows the rules below to coordinate the test based on the locations assigned to the individual monitor, and the default locations used by the company overall when new monitors are created. These locations are not always the same.
The monitor first looks through the locations assigned to the monitor and the account overall to see if the Primary location it uses for Remote Verification exists within this pool of locations. If not, it looks through the same pool of locations for the Secondary location used for Remote Verification.
If neither the defined Primary or Secondary locations exist within this pool of locations, the test will use the next location in that pool for the remote verification test. The location selected would be the next location in ascending order based on location ID, rotating back to the top when the largest is reached.
If the account and monitor use only 1 location and it’s the same, and the pool thus consists of only 1 location. In that case the remote verification is triggered from the Primary location defined for that location.