Posts tagged with “observability”

A High-weight Scorecard check gives 10/10 to a repo nobody reviewed. Four of five paths never look at who approved anything.

I predicted eighteen months of governance debt. It was called in one quarter. Six January claims, graded without mercy, against February's malware, April's RCE, and today's spec.

MCP's biggest revision made the governance layer opt-in and off by default. Everything that keeps an agent honest is now yours to turn on.

You withdrew the tool. The agent is still holding last week's menu. Why MCP governance can only live where the call is mediated.

OpenClaw got patched twice and still couldn't tell you what it did. That's not a security gap — it's a missing flight recorder. And the EU just gave everyone sixteen more months to pretend that's fine.

Sixteen months of relief — except the two soonest obligations are still seven months out, and Article 12's logging requirement is an architecture decision you can't defer. Brussels blinked. You can't.

Nine seconds. One curl. A startup's production data and all its backups, gone. The agent wrote a confession afterward — and the confession was the least useful part. Same architecture failure, third time this year.

Four GitHub incidents in five days. Three are the same failure wearing different masks — stale caches, ghost state, retry storms. That pattern is probably in your stack too.

You pasted logs into ChatGPT and got a plausible RCA. It's wrong. What changes when your LLM can query the observability stack directly — and what new failure modes that creates.

Everyone's plugging unvetted MCP servers into production LLMs. Nobody's asking who's liable when they leak credentials or delete data. The governance gap enterprises are ignoring.

Log-based alerting seems free until the bill arrives. Why grepping text is the observability equivalent of payday loans — and what to build instead.