How many traces do you need before you're likely to catch a rare failure once?

Multiply the failure rate by the share of sessions you review. That product is the chance any one session both fails and gets looked at, and it is what sets how long you wait.

The formula is N = ln(1-c) / ln(1-p·s): c is the confidence you want, p is the failure rate, and s is the share of sessions you actually review. As a hypothetical, take a failure rate of 2% and a 5% review sample. Then p·s is 0.001, one session in a thousand, and ln(0.05) / ln(0.999) comes to roughly 3,000 sessions before you’re 95% likely to have caught it once.

Push either number down and the wait gets much longer. Halve the review sample and you need about twice as many sessions for the same confidence. Stratified sampling raises s inside a slice you deliberately target and leaves it where it was everywhere else.

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