How to monitor a website

Build a monitoring setup that checks what customers actually need to accomplish, not just whether the server responds.

Define the critical action

For define the critical action, focus on the customer-facing result first. Build a repeatable check, keep the test safe, and record enough evidence to tell the difference between a short-lived warning and a real business-impacting failure.

Choose the right frequency

For choose the right frequency, focus on the customer-facing result first. Build a repeatable check, keep the test safe, and record enough evidence to tell the difference between a short-lived warning and a real business-impacting failure.

Verify failures

For verify failures, focus on the customer-facing result first. Build a repeatable check, keep the test safe, and record enough evidence to tell the difference between a short-lived warning and a real business-impacting failure.

Keep useful history

For keep useful history, focus on the customer-facing result first. Build a repeatable check, keep the test safe, and record enough evidence to tell the difference between a short-lived warning and a real business-impacting failure.

A practical monitoring rule

If the failure would cost a lead, booking or order, monitor the complete customer action rather than only the page or server behind it.