6 posts tagged guide. All posts
2026-09-28
Checking an HMAC signature takes three lines, and most receivers still get it wrong by checking it against re-serialised JSON. How to verify okokumo's X-Sentinel-Signature against the raw body in Node, Python and Go, which responses we retry and which we don't, and why your receiver has to cope with the same alert arriving twice.
2026-09-21
Flipping a component to red automatically is easy and usually wrong. What a status page is actually for, why okokumo drafts an incident but never publishes one for you, what to write in the first update when you still don't know what broke, and why "investigating" for four hours followed by "resolved" is a communication failure.
2026-09-14
A job that fails sends you a stack trace. A job that never starts sends you nothing, and nothing looks exactly like success. How heartbeat checks turn silence into a signal — and how to size the grace window so a slow nightly backup doesn't page you at 3am.
2026-09-07
Certificate expiry is the most preventable outage in the industry and it still takes down major products every year. Why escalating D-30/D-14/D-7/D-1 alerts, chain validation, and domain-expiry checks belong in the same monitor as your uptime probes.
2026-09-06
A 200 with an empty body, a stale cache, or a pretty error page is still an outage. How to layer status, latency, body and header assertions so a check verifies the service works — not just that something answered.
2026-08-18
A walkthrough of the first ten minutes in okokumo — set up an alert channel, create an HTTP check, read what it tells you, then publish a status page if you want one.