Uptime monitoring, explained without the jargon

The advice here is unglamorous, which is probably why it gets skipped. Here is uptime monitoring without the vocabulary that usually surrounds it.

The cheapest security work is the boring kind done on a schedule. Budget a little time for it every quarter and it never becomes a project of its own.

The short version

You should not learn about downtime from a customer. Small and consistent beats large and occasional here. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.

Why people complicate it

Most of the confusion comes from tooling rather than from the idea itself. The reasoning matters more than the rule, because the rule has exceptions.

Monitor the checkout, not just the homepage. Small and consistent beats large and occasional here. Check it against what you would want a competitor's site to get wrong.

Making it stick

Alerts nobody acts on are just noise. The cost of getting this wrong is rarely visible on the day it happens. Write the reasoning down alongside the decision, because the reasoning is what changes first.

How to tell if yours is fine

The realistic threat for most small businesses is automated and opportunistic, not targeted. Three things worth confirming about uptime monitoring before you move on:

• Someone can say what the current setup is without going to look
• Alerts nobody acts on are just noise — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Pick the one that would hurt most if it failed, and start there.