What's the difference between observability and evals?

Observability records what an agent did; evals judge whether what it did was right. Instrumentation is what makes observability possible: a span for each LLM call and tool call, a trace for the turn, so you can see the exact inputs, outputs, and steps after the fact. None of that carries a verdict on its own. An eval runs a grader, a deterministic check, a trained classifier, or an LLM judge, against that recorded behavior, or against a separate test case, and produces a pass, fail, or score. You can have deep observability and no evals at all: a complete trace of an agent nobody is checking for correctness. You can also run evals on weak observability, grading outputs without enough recorded context to tell why one failed. A grader needs something to read: observability supplies the trace, and the eval supplies the judgment the trace alone never makes.

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