Can I rename a call-site id later?

You can, but the baseline for that call site starts over. Findings, baselines, and grader synthesis all accrue history under the exact string you stamped, so a rename looks to Tessary like the old call site went quiet and a new one started with no traffic behind it. The wait before drift and cost checks say anything again is the same wait a freshly tagged call site goes through, and any grader grounded in that call site’s traces has to re-ground on new examples. Renaming isn’t destructive, the old id’s history is still stored, just orphaned from anything that keys off the new one. If you’re refactoring code and want continuity, keep the id stable across the move instead of renaming it to match a new function or file name; a stable id is what lets history survive a deploy.

keep reading

More on this.

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 →What happens to a span with no call-site id on it?It still ingests. Tessary just can't bind it to a call site, so drift baselines and grader synthesis skip it until you add the tag.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