What is cause attribution?

Cause attribution is the step from knowing a regression happened to naming the specific change that caused it. Detection establishes that quality dropped; attribution is the investigation that follows, over a finite set of candidates: a code commit, a prompt edit, a model change, a tool whose behavior shifted, or an upstream system the agent depends on.

The investigation narrows that set against evidence. You gather the failing traces into one cohort, line their onset up against the change history, and test each candidate until the ones that don’t hold are ruled out. Failures cluster around the code path that produces them, so when the failing traces share one path, the candidate set shrinks from everything shipped recently to the handful of changes that touched that path in that window.

A finished attribution names the cause, cites the traces and findings that support it, and lists what was checked and ruled out, which is also what tells you where the fix belongs.

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