Does connecting Tessary require installing an SDK?

No. If your agent already emits OpenTelemetry traces, connecting Tessary is a configuration change, not a code change: point your existing exporter at Tessary’s endpoint over OTLP with a connection token in the auth header, and Tessary becomes a second destination alongside whatever backend you already send to. Nothing in your agent’s own logic has to change.

An SDK only enters the picture if your stack emits no OpenTelemetry traces at all yet. Tessary offers a push source for that case, but it’s the fallback, not the default setup path. Once traces are flowing, tagging spans with a call-site id is optional and can be added later; without it, Tessary groups traffic by what the spans already say. One thing worth knowing going in: the duration and cost detectors need real traffic to build a baseline before they report anything, so an empty case list right after connecting means it’s still collecting, not that nothing is being checked.