·3 min read
The engineer who knows everything is a risk, not a hero
Every team has the one engineer who fixes everything. That dependency is a single point of failure with a pulse. How to spread the knowledge before it walks out the door.
Incident articles, page 6
More articles on incident management, monitoring, and on-call.
·2 min read
Single-node monitoring is quietly lying to you
If your uptime checks run from one location, you are seeing one network path, not your users. Why single-node monitoring misses real outages and invents fake ones.
·2 min read
SSL certificates always expire on the worst day
An expired certificate takes your whole site down in a way no code change can fix fast, and it is entirely predictable. Why cert expiry is the outage you can see coming.
·2 min read
What a status page is actually for
A status page is not a dashboard for you. It is a trust tool for your customers, and it only works if it tells the truth when the truth is inconvenient.
·2 min read
DNS fails silently, and you find out last
When DNS breaks, your servers are fine, your usual checks may be fine, and your users cannot reach you at all. Why DNS failures are so easy to miss and how to catch them.
·2 min read
Runbooks people actually use
Most runbooks are written once, never opened, and useless by the time you need them. What separates a runbook that helps mid-incident from one that just exists.