What happens when tool_error flags a tool?

A tool_error detection goes to triage first, which checks whether the rate shift is a real deviation rather than noise or something already explained.

If triage confirms it, the finding opens a case: one record per tool naming when the failure rate started shifting, which failure patterns moved it, and which call sites the traffic came through. That case is what a person is meant to act on, not the raw detection.

From there, once the project has a notification destination configured, the case reaches a human without anyone having to be watching a dashboard: a message with the case, what moved, and why it crossed the bar, sent to that destination. Nothing about a tool_error case is different from any other Tessary classifier’s case at that point; the classifier just supplies the finding.

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