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, grader synthesis, drift baselines, per-call-site assessment, 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.

Can I rename a call-site id later?Yes, but the baseline resets: findings and baselines accrue under the exact id string, so a rename looks like a new, historyless call site.answer →How do I tag a call site so graders can bind to it?Set tessary.call_site.id as a plain span attribute, no SDK required. A Collector transform rule can add it in transit if you'd rather not touch code.answer →How long before a call site's baseline is worth anything?The duration and cost detectors wait for about 150 comparable turns on each side of a call site's baseline before they'll call anything a deviation.answer →Everything on tessary call sitesThe definition, and every question answered under tessary call sites.concept →

Send us the traces you already emit.

book a demo