Skip to main content
OpenLIT instruments AI orchestration frameworks to give you end-to-end visibility into agentic workflows. Each span captures the framework operation type, inputs, outputs, and timing — so you can trace how a user request flows through chains, agents, and tool calls.

How framework tracing works

When you call openlit.init(), OpenLIT patches the framework’s internal execution methods. For each operation — a chain run, an agent step, a tool call, a retrieval — OpenLIT creates an OpenTelemetry span. Setting detailed_tracing=True (the default) captures per-step traces for maximum observability. Set it to False to reduce span volume in high-throughput scenarios.

Get started

1

Install OpenLIT

2

Install your framework

Install the framework package your application uses:
3

Initialize OpenLIT

Call openlit.init() before any framework code runs.

Supported frameworks

Span attributes captured

Framework spans include attributes specific to the operation type:
Enable detailed_tracing=True (the default) to capture individual chain steps and agent iterations. This creates richer traces at the cost of additional span volume.

LLM provider integrations

Trace individual LLM calls with token counts, cost, and latency

Vector database integrations

Trace vector search, upsert, and index operations

Destinations

Send telemetry to Datadog, Grafana, New Relic, and other observability stacks