What happens after the same failure keeps recurring?

If the same cause keeps firing without a real gap, nothing new opens: it’s still the same case, collecting more evidence, because the finding’s onset is frozen for as long as the detection keeps recurring.

A gap is what changes that. If a case has already been resolved and the same cause fires again later, after the detector’s own quiet window has passed, the return is read as genuine rather than as the tail of the original spell, and that’s what reopens the case instead of opening a fresh one next to it. The history of one recurring problem stays in one place. The quiet window is set per detector, hours for a tool failure rate, longer for a duration or cost shift, so how long an absence has to last before it counts as new depends on what kind of problem it is.

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