What’s new in Neatlogs

A span tree shows the shape of a run, but not how it played out. Replay lets you move through it in sequence, where it branched, where it stalled, what each step decided, which is usually faster than reading a static tree when you're trying to understand behavior.

A persistent shell wraps every replay: transport controls, a structure graph, a timeline that exposes concurrency and idle gaps, and an inspector for the selected step. Switch the center between a narrative Story walkthrough and a proportional Tree-plus-gantt view. It runs on your live traces or bundled demo architectures, and reads the same span data as Traces, so anything your instrumentation captures shows up with no extra setup.

A single trace tells you what happened in one run: it won't tell you that p95 latency crept up this week or which model is quietly driving your bill. Analytics gives you that aggregate view and groups recurring failures together, so a regression shows up as a trend instead of a surprise.

The dashboard is built from widgets you can show, hide, and reorder, a KPI strip, cost breakdown by model or workflow, tool latency, error clusters, and detection trends. One filter bar scopes everything by time range, workflow, model, tool, or detection, and every number drills straight back into the traces behind it, since it's all computed from the same span data.