/agents) is OpenLIT’s AI agent observability view: a single place to see every agent OpenLIT has observed, built entirely from your OpenTelemetry trace data - there’s nothing to declare or register up front. As soon as an agent’s spans (including tool calls, model calls, and system prompts) show up in your traces, OpenLIT surfaces it here. See Setup for what it takes to get an agent showing up.
Agents list
The Applications tab lists every agent and service instrumented with the OpenLIT SDK, discovered fromservice.name and gen_ai.* span attributes. Each row shows the service name, host system, runtime, providers in use, and when it was last seen. You can filter by System, Provider, or discovery Status.
Click any row to open its detail view, which has five tabs:
Overview
Metadata grid and the trace-derived call graph
Analytics
Latency, cost, tokens, and errors over time
Monitoring
The agent’s own traces and requests
Definition
Captured system prompt and tools
Configuration
LLM / Agent Observability toggles
Coding-assistant clients (Claude Code, Cursor, Codex, Windsurf) have their own tab and detail layout, since they’re IDE/CLI clients rather than deployed services - see the dedicated Coding Agents section.
Overview and the agent graph
The Overview tab starts with a metadata grid - Requests (24h), Primary Model, Models, Tools, Age, and Last Seen - followed by a DAG (directed acyclic graph) of the agent’s call flow: nodes for span names and tool calls (derived fromgen_ai.tool.name and function-call attributes on LLM spans), edges annotated with call count, p50 latency, and error rate.
This graph is computed live from ClickHouse: OpenLIT samples up to 500 recent traces for the agent and self-joins the spans to build an aggregate call graph. It is entirely trace-derived - there’s no static or declared workflow definition behind it, so the graph always reflects what the agent actually did, not what it was designed to do. The graph always shows one specific version’s traffic - the version selected in the header, or the latest version if you haven’t picked one - see Versioning for how that differs from the other tabs.
Frequently asked questions
Do I need to register or declare my agents?
Do I need to register or declare my agents?
No. Every agent, its call graph, tools, and versions are discovered automatically from OpenTelemetry trace data - there’s nothing to register up front.
How is the agent graph built?
How is the agent graph built?
OpenLIT samples up to 500 recent traces for the agent and self-joins the spans into an aggregate call graph, with nodes for span names and tool calls and edges annotated with call count, latency, and error rate.