Urgent.News

What's breaking now, across thousands of outlets.

Tech

We Designed a Monitoring Stack, Then Decided Not to Build It

The plan was a good plan. Continuous frontend performance monitoring for 30 to 40 WordPress sites: sitespeed.io runners on Hetzner Cloud, a time-series store, artifacts in object storage, Grafana on top, all of it in Terraform. Three architecture decision records worked through runner topology and sizing, the split between time series and artifacts, and a two-tier regression detector with budgets…

The plan for continuous frontend performance monitoring for 30 to 40 WordPress sites involved using sitespeed.io runners on Hetzner Cloud, a time-series store, artifacts in object storage, Grafana on top, all set up through Terraform. After working through the architecture decision records (ADRs) on runner topology, sizing, and a two-tier regression detector with budgets and baseline deviation, the fourth ADR questioned whether building this stack was worth it, ultimately retiring the entire build.

Compared to buying Grafana Cloud Synthetic Monitoring, the self-hosted stack would run around €4,900 in year two, with only €1,300 being infrastructure costs. The break-even point for building the stack would be around 600 URL profiles, roughly 100 sites, making it about two and a half times the current estate. The mistake in earlier calculations was not considering the cost of own time, which was implicitly priced at zero but should have been priced at €800 per day.

The self-hosted option's break-even point depends on scale, and only makes sense at a scale of around 600 URL profiles, or about 100 sites. The decision record for the build should include this condition, along with the fact that it is not a decision to be made, but rather a build instruction for when the condition is met. Arguments for building the stack included data sovereignty and the learning effect of building a Terraform/Hetzner stack, but these arguments did not survive as they were not relevant to the current scale of operations.

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

Read the original at dev.to →

More in Tech

Two Rewrite Changes That 404'd Every Post on This Blog

An SEO audit of this blog turned up a list of small, unglamorous findings. /blog/ returned 404. Category archive URLs contained a literal /./ segment — /blog/./wordpress-performance — while tag…

  • Category archives 404-ed, causing blog outage
  • Author archives and posts inaccessible after incident
  • Resolved by changing categorybase to empty value

How to add an MCP server to VS Code (mcp.json, .mcp.json and fixes)

How to add an MCP server to VS Code Checked against the official docs: Oct 28, 2026 VS Code's agents can call tools from MCP (Model Context Protocol) servers, for example to drive a browser, read…

  • Use MCP: Add Server command in VS Code's Command Palette
  • Choose ID, save location, and provide trust/sign-in info
  • Add server via guided flow, gallery, or manual config file

Cursor rules vs AGENTS.md: which to use (and .cursorrules)

Cursor rules vs AGENTS.md Checked against the official docs: Oct 27, 2026 Cursor gives you three ways to hand your coding agent standing instructions: project rules in .cursor/rules , an AGENTS.md…

  • AGENTS.md is a markdown file for project instructions, supported by multiple coding agents.
  • .cursor/rules/.mdc files are Cursor-specific rules for certain situations, scoped by globs.
  • .cursorrules is legacy and will be deprecated, migrate to .cursor/rules/.mdc format.

Run your coding agents in tmux and let a local model tell you which replies to read

In two weeks I sent my coding agents 1,523 prompts and read every closing message. I was fed up, so I put a small local model in front of them. It left me 696 to read. The tool is TLDRack.

  • Author ran 1,523 coding prompts, reviewing all outcomes
  • Integrated open-source tool TLDRack to assist agents
  • TLDRack uses local model to grade agent replies

More from Friday 20 November →