Glossary

Trace (observability)

On this page

The short answer

  • A trace is a recorded sequence of steps in an LLM application — model calls, tool calls, retrieved chunks, latency and cost — used to debug live or staged runs. Observability platforms are built around traces; a prompt tester is not.
  • This is a glossary entry, not a product claim or a benchmark result.
  • All terms · Templates · Guides.

Definition

A trace is a recorded sequence of steps in an LLM application — model calls, tool calls, retrieved chunks, latency and cost — used to debug live or staged runs. Observability platforms are built around traces; a prompt tester is not.

In practice

Litmiq does not record production traces. Each run lives in your browser unless you export it or pack scores into a share link (which stays in the URL fragment and is not stored by Litmiq).

When a failure only appears in a multi-step live run, copy the last prompt and the context into a Litmiq case so it cannot silently return.

FAQ

Does Litmiq implement “Trace (observability)” as a built-in metric?

Only where the definition itself says so. Many terms are industry vocabulary. Litmiq is a single-turn, BYOK prompt tester with an LLM judge, not a full evaluation platform.

Where is the rest of the glossary?

The hub at /glossary lists every term. This page is the standalone entry for Trace (observability).

See the term in a suite

Many glossary entries have a matching template you can run in the browser.

  • Free, no signup
  • Runs in your browser
  • Your OpenAI key, sent only to OpenAI

Follow Litmiq on LinkedIn