< 5 min
setup
OTel native
OTLP/HTTP
100 events
per batch
1.0 Tracing
Trace Explorer
What you get
A filterable, sortable list of every trace — latency, cost, status, model, agent, and operation in one view. Click any trace to open the span waterfall: the full parent/child hierarchy with exact timing, tokens, and cost per span.
2.0 Tracing
Session Grouping
What you get
Traces sharing a session_id are grouped into conversation sessions automatically. See total cost, token counts, error rate, and a first-message preview per conversation — no extra instrumentation.
3.0 Tracing
OpenTelemetry Ingest
What you get
Native OTLP/HTTP endpoint at /v1/otel accepts standard OTel spans, resource attributes, and instrumentation scopes. Plug in any OTel-compatible framework without changing how you instrument.
4.0 Tracing
AI Root Cause Analysis
What you get
Click 'Analyze' on any failed trace and Zespan runs AI-powered root cause analysis over the full span tree — returning a structured explanation of what failed, which span is the root cause, and why.
Setup
Under 5 minutes,
two lines of code.
No forking and no architecture changes. Traces appear within seconds of the first agent run, with cost attribution, eval scores, and anomaly alerts on by default.
Common questions
Does adding the SDK affect my app's latency?
No. Traces are sent asynchronously — events are queued in the background and written to ClickHouse by a worker process. The SDK adds zero latency to your LLM calls.
Do I need OpenTelemetry to use Zespan?
No. The SDK's wrapOpenAI(), wrapAnthropic(), and similar wrappers handle instrumentation automatically. OpenTelemetry is an alternative path if you're already using OTel or want to use the OTLP/HTTP endpoint directly.
What frameworks does tracing support?
OpenAI, Anthropic, Google GenAI, Bedrock, Groq, Mistral, OpenRouter (provider wrappers), plus LangChain, CrewAI, AutoGen, Google ADK, LlamaIndex, Vercel AI SDK, and PydanticAI (framework handlers). OpenTelemetry covers any other framework.
How long is trace data retained?
Retention depends on plan: 14 days (Free), 30 days (Solo), 90 days (Pro), 180 days (Team). Enterprise retention is configurable.
Is my LLM call data used to train models?
No. Your trace data is never used for model training by Zespan or shared with any third party.
Explore more features
All features →
