See what your AI is doing. Make it better.

Follow every trace, find what went wrong, and turn real examples into evaluations. One place to understand and improve your AI workflows.

Traces. Evaluations. A better next version.

Every step. Nothing hidden.Follow one request through retrieval, generation, and verification. Illustrative workflow, not live customer data.ai.agentretrieve4 documentsgenerate1 model callverify1 flagged answer

Every step. Nothing hidden.

Follow one request through retrieval, generation, and verification.

TracesExample workspace
Trace log rows. Press Enter or Space on a focused row to open its inspector.
NameInputOutputDurationInput tokensOutput tokensEstimated cost
support.agent
4 spans

generate.answer

Input tokens
1,248
Output tokens
164
Estimated cost
$0.00076
Input
user

Can I return my order after 45 days?

tool

Returns are accepted within 30 days of delivery.

Output
Yes! You can return your order within 60 days.
Follow a sample request through Datool’s trace log and span inspector.

THE IMPROVEMENT LOOP

From a single request to a clearer picture.

Follow every trace

Inspect inputs, outputs, spans, latency, and scores in the context of the whole workflow.

Evaluate real examples

Build datasets from the cases that matter. Test changes with repeatable evaluation runs.

Make quality visible

Use scorers, human reviews, and dashboards to understand how your application performs.

Start with the evidence you already have. Trace a workflow, review an unexpected result, and keep that example as a test for the next change.

TRACES02

Find the step. See the evidence.

An answer alone cannot explain a failure. Open its trace to see the recorded inputs, outputs, and timing for each model call and tool.

↳

Follow the execution

Move through the span tree and timeline to understand which steps ran and how they relate.

↳

Find the useful signal

Filter requests by status, timing, metadata, and scores. Save the views you return to.

Explore traces
support.agent 2.8s4 spans
search.documents1900ms
Output
{ "policy": "Returns are accepted within 30 days of delivery.", "source": "returns-policy.md" }

Search takes 68% of this run. It found the correct 30-day return policy.

AGENTS & WORKFLOWS03

One workflow. Many decisions.

Follow the relationships between workflows, agents, and the tools they call. Group related runs to see whether a problem is isolated or keeps coming back.

↳

Group related runs

Named agent groups connect invocations across traces, keeping the agent’s identity separate from individual span kinds.

↳

Compare performance

Explore operation counts, latency, errors, and recorded cost across agent names and versions.

Explore agents

Keep the relationships in view

customer.supportworkflow
triage.agentClassify the request
support.agentRetrieve → answer
Group by agent or workflow. Investigate the individual run.

DASHBOARDS04

Start wide. Then ask a sharper question.

Compare quality, latency, usage, and estimated cost across your recorded activity. Filter by workflow and time range, then inspect the records behind the metric.

↳

Choose what matters

Combine reusable widgets for request volume, latency, model usage, recorded cost, and evaluation results.

↳

Keep the context

Use date ranges and filters to narrow the view and share the same investigation context.

Explore dashboards

P95 latency for each step of your application.

generate.answer
search.documents
verify.sources

Daily span volume by operation.

generate.answer
search.documents
verify.sources

THE OBSERVE TOOLKIT

From a surprising answer to the reason behind it.

A few things you might be wondering.

How does Datool connect to my application?

Use the Datool SDK to record workflows, model calls, and tool calls, or add Datool's span processor to your existing OpenTelemetry setup. You can also connect an application for dataset evaluations without the tracing SDK. Instrumenting the steps inside it gives you the detailed trace.

What can I see inside a trace?

Follow a request through its recorded steps, with inputs, outputs, timing, errors, and scores in context. For instrumented model calls, Datool also shows reported token usage and cost estimates when usage and pricing information are available. Related traces can be grouped into sessions.

Can I turn a real failure into a test case?

Yes. Save useful examples from recorded traces into a dataset, add reference answers where needed, and use those cases in evaluation runs. That unexpected answer becomes a repeatable check for the next version of your workflow.

What can I evaluate?

Use recorded traces or dataset cases to evaluate your AI workflows. Combine code-based and LLM scorers with human reviews, then compare results across evaluation runs.

How do I decide what a good answer looks like?

Choose a built-in evaluator, write a JavaScript or Python scorer for a precise rule, or use an LLM scorer with your own rubric. Test the scorer on representative examples before running it across a dataset. Human reviews can add ratings and comments alongside automated judgments.

Can I compare different prompts or models?

Yes. Run the same cases against different application versions or prompt and model settings supported by your app. Compare scores and individual outputs to see which cases improved or regressed. You can also re-score saved outputs with a different scorer without calling the application again.

Can my team review answers manually?

Yes. Create a review session from selected traces, define the ratings that matter to your team, and inspect each answer in context. Reviewers can save scores, leave comments, and annotate specific parts of the input or output. Those judgments complement your automated evaluations.

START WITH ONE REQUEST

Your next improvement starts with a trace.

Get started with Datool