#observability
Every post tagged "observability".
40 posts · showing 11–20
-
Read-Only Was Never the Same as Safe
SELECT-only credentials close exactly one of the four ways an analytics agent can hurt you. The other three don't require the ability to write anything to the database at all.
-
Your Trace Store Will Outgrow Your Model Bill
Storage passed inference cost in three weeks, and the proposed fix — sample at 5% — would have discarded exactly the runs worth keeping. A trace isn't one artifact with one lifetime.
-
Evaluation Engineer: The Job Description Writing Itself
The furthest-formed of the emerging roles: well-defined, consistently needed, consistently unstaffed. It's everyone's dependency and nobody's job, which is exactly why.
-
Agent Operations: The Role Without a Title Yet
Someone in every agent-running organization does this job without being hired for it. It has no name, no allocation, and no incident that forces it — until whoever was doing it informally leaves.
-
What Distributed-Systems Experience Transfers to Agent Loops
An agent run is a distributed system with unreliable participants, so most of the discipline transfers. Four things twist — and one microservice instinct actively hurts, because agent boundaries are lossy.
-
How to Benchmark Models on Your Own Task
Public benchmarks tell you about a model, not about your system. Frozen tool responses, assertions written from the requirement, and four numbers instead of one — plus the shortcut when a full suite isn't happening.
-
Which Agent Alerts Should Wake Someone Up?
An agent can be green on every service metric while doing the wrong work at ten times the cost. One rule sorts the alerts — and the highest-value one is the one almost nobody has configured.
-
From Prompt Edit to Signal in Under a Minute
A six-minute iteration buys you ten experiments a day; a thirty-second one buys a hundred. Four fixes, about an afternoon of work, and the seam that everything else depends on.
-
How Many Eval Cases Do You Actually Need?
18/20 versus 19/20 is not an improvement — it's noise wearing a number. What your suite size can and cannot detect, and the paired design that makes a hundred cases behave like seven hundred.
-
One Query Is Rarely Enough: Iterative Retrieval for Agents
The search wasn't broken — it answered the question as typed, which isn't the question that was asked. Making retrieval a tool the agent calls repeatedly needs one signal most retrievers refuse to give.