Monitoring

Know when something breaks before your users tell you.

Monitoring tools are what tell you something broke before a user has to report it, covering uptime checks, error tracking, and performance metrics. Error tracking catches exceptions with enough context to actually debug them; uptime and performance monitoring catch the broader health of the system. A minimal setup here pays for itself the first time it catches something before a user does.

Better Stack

Started as uptime monitoring and grew into a full observability platform (incidents, status pages, on-call, logs). A good one-stop shop if you don't want five separate monitoring bills.

↗

Checkly

Synthetic monitoring where your checks are actual TypeScript/Playwright code living in your repo, not a point-and-click config screen.

↗

Pingdom

One of the oldest names in uptime and page-speed monitoring. Solid if you want a battle-tested tool, though the free tier is gone now.

↗

Sentry

The standard for error tracking. Groups errors by stack trace, links back to the exact commit and line, and now covers performance and session replay too.

↗

UptimeRobot

The cheapest, simplest way to know when your site goes down. Free tier covers 50 monitors, plenty for a solo project.

↗