Why do quality layers built on an LLM judge end up sampling instead of grading everything?

A generative judge makes a paid inference call on every trace it grades, and that cost scales linearly with traffic. A tool that grades everything with one has to either sample or accept a bill that grows with usage, and sampling is the cheapest lever available once a judge is the only grading method in play: cut to 10% of traffic and the bill drops by 10x, no other engineering required.

The tradeoff is what sampling always costs. A failure that shows up in 1% of traffic is unlikely to land in a 10% sample, so whatever the sample misses stays invisible until enough of it accumulates to notice. Doing the cheap grading, deterministic checks or a distilled classifier, on all of it and saving the judge for a flagged slice avoids that tradeoff, but only if something upstream of the judge is actually cheap.

keep reading

More on this.

Two ways to run Tessary.

Tessary is an open-source agent reliability platform. Cloud and self-hosted run the same workflow on the OpenTelemetry traces your agent already emits.

Tessary Cloud

We host it for you. Send your first trace with nothing to deploy and no model key.

what's includedper organization
traces
10,000 per calendar month
stored trace data
1 GB
retention
30 days
model credit
$10, one-time, for triage and root-cause analysis
credit card
not required

Self-hosted Tessary

Run the open-source code on your own infrastructure with one command. Add your own model key for triage and root-cause analysis.

Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md

docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y