Page people on what users can feel — error rate, latency past an SLO — not on causes like CPU, and only when the page includes a next step. Use when creating an alert, after a noisy night, or when the board is red and nobody is moving.
--- name: page-on-symptoms category: coding description: >- Page people on what users can feel — error rate, latency past an SLO — not on causes like CPU, and only when the page includes a next step. Use when creating an alert, after a noisy night, or when the board is red and nobody is moving. --- # Page on Symptoms A page is an interruption of a human's sleep or focus. It is expensive. The only honest reason to spend it is: **a user-visible job is failing, and a person can do something in the next fifteen minutes that a script cannot.** CPU, disk, "instance unhealthy," and "restart count" are **causes** (or not even that). They belong on a dashboard. They do not belong on a phone at 3am unless you have already proven they are the symptom by another name.
You are reading the opening of this skill.
The rest is open to any signed-in account — free included. Reading the library costs nothing.
Shared publicly by the author and open for any use. See the Terms.