OpenTelemetry
Vendor-neutral tracing standard — I ship an OpenTelemetry exporter in Akashi and trace agents with it in client work.
OpenTelemetry (OTel) is the open standard for traces, metrics and logs. For LLM systems it turns each agent run, model call and tool call into spans that any compatible backend can display.
How I use it
- Akashi — the
akashi_otelpackage exports OpenTelemetry traces for agent runs; together with per-call token usage accounting it is part of the framework's operability story. - Conversational AI Agents — Langfuse/OpenTelemetry tracing across a multi-tenant agent platform in my Independent AI & Full-Stack Engineer (Freelance) work.
Why it matters
Agent runs are trees of model calls, tool calls and sub-agents. Emitting them as standard OpenTelemetry spans means the same traces can land in Langfuse or any other OTel-compatible backend, without coupling the runtime to one vendor — the same provider-neutral stance Akashi takes with models.
For me, tracing is not an afterthought: Akashi ships an OpenTelemetry exporter next to per-call token accounting, and my freelance agent work pairs tracing with automated Evals.