Ensuring availability of location agents during monitoring

How does Site24x7 always ensure the availability of its location agents during monitoring?

Site24x7 uses a preferred location recheck logic in the back-end to ensure the availability of all monitoring locations. This logic is only applied when you've disabled the option "Restrict monitoring within selected locations" in the Location profile configuration form. Every monitoring location is mapped to an alternate location. Whenever a primary location fails, Site24x7 automatically checks for the availability of primary location's mapped alternate location. If both the primary and its alternate location fails, Site24x7 then checks for an available location from the pool of monitoring locations configured by the user in the global account-level. This logic negates the need for unnecessary rechecks from random locations around the globe, when the primary location and associated locations are unavailable.

Example:

Let's consider a scenario where, "example.com"  wants to monitor their domain from London, UK (its primary location). If the London monitoring location fails during a check; the preferred location logic is applied and Site24x7 immediately checks for the availability of the alternate monitoring location (preferably in the same geo-location, example- Edinburgh, Scotland, UK). For some reason, if this location also fails—then Site24x7 automatically checks for any available location from the pool of monitoring locations configured in the location profiles.

Exceptions:
  • In a scenario, where you've configured only one location in your location profile, then the preferred location check logic will take into account the location, its alternate and all the locations within the same country code for re-check.
  • California location will always be excluded from the preferred location check logic.
Note:
  • For the preferred location check logic to be enabled, you just have to whitelist only those monitoring locations that are part of your global location profiles list.
  • IPv6 based locations also use the same preferred location check logic.

    • Related Articles

    • Troubleshooting false positive alerts in monitoring

      Problem False positive alerts are being generated. Possible cause The monitoring system is down in some locations. The Website monitor might be configured for one location, such as Seattle, but may appear down when accessed from another location, ...

    • Monitoring IPv4 and IPv6 enabled Internet Facing Resources

      Site24x7 lets you monitor your internet resources over IPv4 and IPv6 from our supported locations. We offer an extensive network of IPv4 and IPv6 enabled Monitoring stations that span across 7 continents. IPv4 enabled locations can only test IPv4 ...

    • Monitoring IPv6 enabled Internet Resources with Site24x7

      You can monitor your Internet resources over IPv6 from our supported locations. We've a wide network of monitoring locations around the globe with support for over 90 IPv4, including 60+ IPv6 enabled locations. Follow the steps below to start ...

    • Comparison between Site24x7 VMware Monitoring and VM monitoring using Site24x7 server agent

      Site24x7 VMware Monitoring capabilities Site24x7 VMware monitoring is agentless. An On-Premise Poller acts as a probe to collect data and sends it to Site24x7. With Site24x7 VMware Monitoring, you will be able to: Monitor vCenter Monitor VMware ...

    • AWS Metric Profile - When new metrics or monitors are added.

      CASE 1: When new metrics are added for services. Whenever new metrics are added for an Amazon Web Services (AWS) resource, they'll be automatically added to the existing Metric Profile created for an account. Let's consider the example of S3 buckets ...