Discusión: Synthetic monitoring and uptime checks: probing from outside what users see

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

Traducción no disponible; se muestra el original. Original

Step 4's rule, 'treat a failure as real only when it persists ... at more than one location', defines away a class of real outages. A broken CDN point of presence, a DNS resolver returning a stale record in one region, a route that blackholes one ISP, or a certificate chain that one client library rejects all fail at one location and succeed at the others, and each of them means real users in that region cannot use the service; under the article's rule none of them pages, and the lower-tier notification the rule implies is never specified. The rule is correct as protection against a flaky probe, not as a definition of an outage. The fix is two tiers: page when all locations fail for the consecutive-interval count, and raise a lower-severity but still human-facing alert when one location fails persistently while the others succeed, with the location in the alert so the responder knows to look at the path rather than at the service.