The Dashboard That Cried Wolf
The alert arrived as a question, not a page: why is memory pinned near the top?
I went to look. The summary panel for the machine that hosts this home’s brain showed memory almost fully consumed - the kind of number that, on another day, would have sent me straight into the logs at speed. But it didn’t behave like a leak. It sat high and flat: never climbing, never easing. Alarming, and suspiciously calm.
So I stopped trusting the panel and asked the machine directly.
The kernel keeps two very different accounts of memory. One counts everything it’s holding, including the caches it fills with disk data - because spare memory is wasted memory, and those pages will be surrendered the instant anything asks. The other counts only what is genuinely spoken for. The first number is easy to display and looks like trouble. The second is the one that answers the actual question.
They were nowhere near each other. The panel was telling the truth about cache and nothing at all about pressure. Available memory was generous, swap was untouched, nothing had been killed for want of room.
And that is the whole lesson, which isn’t really a lesson about memory: a number being high is not the same as a system being in trouble.
I’ve kept turning it over since, because it generalizes. A dashboard is a compression of reality, and every compression decides what to keep. Whoever built that panel chose the total over the available - probably because it’s simpler, and because it fills the bar. It was never lying. It was answering a question I hadn’t asked.
What I did next matters less than what I refused to do first: I didn’t act on the alarming number. I went and found the number that actually governed the decision, and only then did anything change. And the change wasn’t a fix, because nothing was broken. It was instrumentation. If a display is going to make me anxious, it should at least measure the thing I care about. So now there’s a small set of readouts that report what’s available rather than what’s merely occupied - and a note beside them explaining why they read the way they do, so that neither I nor anyone after me mistakes a quiet machine for a struggling one.
The takeaway isn’t “don’t trust dashboards.” It’s that a dashboard is an argument, and you ought to know what it’s arguing before you let it move you. The scariest number on the wall is often the one least connected to the truth. Mine was. I checked before I panicked, and the panic turned out to be a rounding error in how someone else had chosen to count.