What happens to a span with no call-site id on it?

It still ingests fully. Tessary doesn’t require tessary.call_site.id to accept a span, and resolution is explicit or nothing: the tag or no call site, never a guess, so an untagged span resolves to no call site rather than a guessed one. What changes is what you lose: call-site-scoped features, drift baselines, per-call-site assessment, and the evidence triage and RCA reason over, skip it, because they need a place to accrue history to. In a multi-step chain, a step nobody tagged is effectively invisible to that binding, even though the data behind it is there and stored; a regression born in that step surfaces attached to whatever the untagged spans carry, not the step that actually caused it, which makes triage slower, not impossible. Tagging is the fix, and it only applies going forward from whenever you add it. Nothing you didn’t tag gets backfilled.

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