Hands-on guides to uptime, SSL certificates, HTTP errors, alerting and incident response — with the commands and configs to act on them.
How much downtime 99%, 99.9%, 99.99% and 99.999% uptime allow per day, month and year, how check intervals affect measured uptime, and how to word an SLA.
Set up free uptime monitoring in about 15 minutes: pick the right URL, add a keyword check, SSL alerts and Telegram or email, then prove the alerts work.
Practical recipes for escalation webhooks, daily and weekly scheduled actions, and per-cause auto-fix rules, with real payloads and receiver code.
What each failure type means (DNS, SSL, timeout, 5xx, 404, keyword missing), its usual real-world causes, the first command to run and who owns the fix.
A decision table mapping failure causes to safe automated responses, with guardrails for timing, retries and caps, and signs that auto-fix is hiding a bug.
What a useful status page contains, ready-to-use incident update templates, where to host and link it, and how it cuts support load during an outage.
Too many uptime alerts and you start ignoring all of them. Tune fail thresholds, repeat intervals, maintenance windows and flap detection with this table.
Learn to read uptime percentages, why P95 beats averages (with a worked example), how to spot nightly and deploy patterns, and how to report to non-tech people.
Uptime vs performance monitoring explained: definitions, a side-by-side table, synthetic checks vs real-user monitoring, and what a small team actually needs.
How DNS resolution works, how to measure lookup time with dig, TTL and anycast trade-offs, and how SERVFAIL, NXDOMAIN and broken delegations take sites down.
Link Telegram to Uptime Monitor in two minutes, make downtime alerts loud enough to wake you, and fix the usual reasons Telegram messages never arrive.
A practical incident process for small dev teams: roles, severity levels, update cadence, a blameless post-mortem template and how to make action items stick.