Terraform Applied Cleanly and Measured Nothing
A successful apply means the checks were written, not that anything is being measured. Then the dashboard went red on every panel except one — and that one exception was the entire diagnosis.
Who merges so late, past midnight's chime, still pushing bugs to master's line?
A successful apply means the checks were written, not that anything is being measured. Then the dashboard went red on every panel except one — and that one exception was the entire diagnosis.
Sixty-one monitored URLs reported time to first byte. Nine reported Largest Contentful Paint. The nine weren’t a random sample — they were the last page of each check script, which is the entire explanation.
A vendor cap of ten browser checks per tenant, undocumented on the pricing page, against sixty-one URLs. The workaround turned out to be the cheaper design — and the labels you assign never reach the metrics you want to filter.
Three architecture decision records planned a self-hosted performance-monitoring stack in detail. The fourth one priced it against the market and killed it — because the servers were never the expensive part.