Traces are the core of neatlogs. Every agent run is captured as a full span tree, LLM calls, tool invocations, retrievals, with inputs, outputs, timing, and cost.
Understand every agent run from end to end
See the complete execution path behind every request.
Neatlogs captures each agent run as a trace, showing the full span hierarchy, execution order, and where time was spent. Inspect prompts, completions, token usage, costs, timing, and other metadata for every span.
Whether you're debugging failures or investigating performance, traces give you the context you need to understand what happened.