Skip to main content

2 posts tagged with "agent-tracing"

View All Tags

How LiteLLM Lens finds repeated failures across 1,000s of agent traces

Moe Khalil
Product Engineer, LiteLLM

A research agent can finish a report after reading the first 8,000 characters of each page. If its web tool cuts off a source and the agent fills in the gaps, you get a completed run with unsupported claims.

Across thousands of runs, you need to find the affected sessions and what they have in common. LiteLLM Lens uses agents to do that work.

Here's how it works behind the scenes: reviewers inspect executions in parallel, grouping agents connect related observations, and investigators check each candidate pattern against the original traces.

Launching LiteLLM Lens

Ishaan Jaffer
CTO, LiteLLM
Moe Khalil
Product Engineer, LiteLLM
Tin Lo
Founding AI Product Engineer, LiteLLM
Yujong Lee
Senior SWE, LiteLLM
October 1, 2026

LiteLLM Lens

Agent swarms200K+ traces from every agent
LiteLLM gatewayevery call, one chokepoint
Lensinsight flows back to your agents

The gateway that helps your agents improve

  1. [1]The agentic swarm developer
  2. [2]The problem
  3. [3]Our solution
  4. [4]Launch partners
  5. [5]Get started
Published:
Ishaan JafferCTO, LiteLLMMoe KhalilProduct Engineer, LiteLLMTin LoFounding AI Product Engineer, LiteLLMYujong LeeSenior SWE, LiteLLM

Today we're launching LiteLLM Lens. Tell Lens what to look for in your agents, let it analyze your traces, then read the findings and go deeper into any trace

The agentic swarm developer​

We're building for a future where developers run agentic swarms: hundreds of agents working in parallel, each one making LLM and tool calls, together generating 200K+ traces

LiteLLM is already the chokepoint for 100% of your enterprise's AI traffic, so every one of those calls already flows through the gateway