What is a root-cause report?

A root-cause report is what Tessary’s RCA investigation produces once it finishes with a case: a set of hypotheses for why the case happened, each one backed by the trace evidence behind it, plus the checks the investigation ran and ruled out so engineering doesn’t repeat them. It names the files involved rather than describing the problem in the abstract, because a report someone still has to go locate the code for isn’t much of a head start. It isn’t a single verdict; a case can genuinely have more than one plausible cause, and the report shows its work on all of them rather than picking one to sound decisive. Where a hypothesis is grounded enough to act on, the report names it. Where nothing clears that bar, it says so instead of guessing. Either way, the report itself is the deliverable, its hypotheses and ruled-out checks are what a person acts on next.

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