How long before Tessary's frustration classifier starts judging a call site?

Tessary’s frustration classifier starts judging a call site once its learned reference holds 100 scored conversations, down from the 200 it used to require, and the reference now keeps learning from every conversation after that until it reaches 1,000, instead of freezing the moment judging begins.

Before the reference holds those first 100 conversations there’s nothing to compare a call site’s current rate of frustrated conversations against, so nothing is judged yet. A call site too quiet to reach 100 conversations inside the 28-day replay window is never judged at all, and its Tuning row reads learning n/100. The lower start exists because a call site that had to wait for 200 conversations went a long time before a new project saw its first finding. The same tradeoff shows up in how long a call site’s cost and duration baseline take to become trustworthy: a classifier is only useful once it has watched enough of a call site’s own traffic to know what normal looks like there, and a lower starting count trades a slightly noisier first few hundred conversations for a usable answer sooner.

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