Urgent.News

What's breaking now, across thousands of outlets.

Tech

Your Health Checks Are Verifying the Wrong Thing

Four production faults passed every health check. An engineer explains how shallow validation hid incorrect metrics, stale data, and exposed credentials.

Your Health Checks Are Verifying the Wrong Thing

Four bugs were discovered in one week, all of them passing monitoring checks. Each of these bugs was the same issue. The first bug involved a financial figure that was off by 16 times. A metric remained frozen for a month while appearing to update. There were nine decommissioned processes still holding live credentials. Additionally, there were 149 backup files that were serving secrets over HTTP to anyone who asked.

All of these issues passed the monitoring process without any problems. The problem lies in the fact that the monitoring checks were verifying the existence of something rather than its accuracy. The author claims that anyone who runs scheduled jobs, agents, or health reports has likely written this bug. The author provides an example of reporting monthly recurring revenue on an internal dashboard, where the number was wrong by a factor of sixteen for weeks, despite all monitoring checks passing.

The author emphasizes that reconciling against source data requires a second source, a join, and a tolerance, which was not done in this case. The author points out that a dashboard appearing green even when it is wrong is worse than one appearing red because green can create false confidence in a number that has not been checked.

The author then recounts three more instances where similar monitoring issues occurred, including a frozen metric, a weekly job that wrote the previous value forward due to an API failure, and decommissioned agents retaining access due to shared global secrets. In each case, the monitoring checks verified the existence of something rather than its truth.

The author concludes by outlining four rules that, if implemented, would have caught all of these issues. Every metric should carry its source and the time it was last genuinely verified, rather than the time it was last written. A value without provenance should render as unverified rather than as a number. The author stresses that green should mean reconciled against something independent, not just a formatting assertion.

Written by urgent.news from HackerNoon's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at hackernoon.com →

More in Tech

I stopped rewriting the same Electron boilerplate — so I packaged it

Every Electron side project starts with the same three weeks. You wire up window controls, and they look wrong next to the OS chrome. You build a theme system and half your components don't follow it.

  • Author packages Electron boilerplate into reusable framework called electron-shell-framework
  • Framework provides top bar, left sidebar, right panel, and bottom terminal strip
  • Includes dark/light themes, encrypted settings, and robust security measures

More from Monday 21 September →