What is a call site?

A call site is the place in source code where a function is invoked, as distinct from where it is defined. Tessary borrows the term for the place an LLM call or a whole agent loop runs, because that is where a finding, a baseline, and a fix attach.

Tessary resolves a call site from one span attribute and nothing else:

tessary.call_site.id: "<your id>"

Untagged spans still ingest, they just don’t get a call site, so nothing about them accrues to a baseline.

Two call sites doing the same kind of work, summarizing two different documents say, stay separate when they’re different places in your code. The id names the function, not the request, so everything Tessary learns about that function accrues to one place: its normal latency, its normal cost, its normal behavior.

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