Watch the right failure.

Map each important customer task to a specific observation and an explicit blind spot. A green check is not a whole-business guarantee.

Use an HTTP check for an expected response and a keyword condition for expected returned content. Neither alone proves a complete customer journey.

Choose a marker tied to the intended page condition, then document what a match and a miss mean. Avoid routinely edited copy.

A home-page response is evidence about that page. Checkout, forms and bookings need separately defined, safe verification.

A certificate and a domain registration can expire independently. Keep separate owners and renewal evidence for each.

A DNS alert identifies an observed record condition or change. It does not by itself tell you whether the change is authorized or harmful.

Use response-time observations to investigate a defined endpoint trend. Do not substitute them for a complete visitor experience test.

A heartbeat reports that a configured signal arrived. Make sure the signal represents the outcome you intended—not merely that a script started.

Monitor only permitted public surfaces and interpret them narrowly. A third-party response does not grant control over that provider or prove every transaction works.