Two rejected series stalled all my metricsTL;DR. Three alerts fired while production was healthy. My metrics account had gone over its active series limit, because a rate limit plugin in Caddy publishes 13 series for every client address. The10 min read·uptimepage.hashnode.devNov 12
"Unable to verify the first certificate": when Node's --use-system-ca hint won't help"TL;DR. Node's "unable to verify the first certificate" error now ends with a hint to try --use-system-ca. The flag helps when a root CA is missing and installed in the system store. It cannot help whe7 min read·uptimepage.hashnode.dev1CNov 4
How to get alerted when someone changes your DNS recordsTL;DR. Most DNS changes do not take your site down. A new MX record or an edited SPF record usually still resolves, so your uptime checks stay green. To catch these changes, list every record a name s9 min read·uptimepage.hashnode.devOct 23
Google says on-call needs eight engineers. You have three.TL;DR. Google's SRE book works out that a 24/7 on-call rotation needs at least eight engineers. A team of two or three cannot reach that number, so it has to change what the number is built from: whic11 min read·uptimepage.hashnode.dev1AOct 6
Uncle Bob's uml-viewer on Rust: 35 dependency cycles down to 3TL;DR. Uncle Bob released uml-viewer, a clickable architecture diagram that draws Dependency Rule violations in red and is meant to be driven together with a coding agent. It only parses Clojure, so I15 min read·uptimepage.hashnode.devSep 22