// UNDERSTAND · TRACE ENRICHMENT
Your traces know what happened. Your data knows if it mattered.
Attach internal context such as user, account tier, version or any custom metadata to every trace with plain span attributes. Then slice quality, cost and evals by the dimensions your business runs on.
THE PROBLEM
A trace without context is just timing
Knowing a run took 4.2 seconds is trivia. Knowing it was a premium customer's checkout, on last week's release, in the EU region? That's the difference between a dashboard and a decision.
// HOW RUNAGAIN SOLVES IT
Session, conversation, user, agent, environment, version, release, tags and a free-form metadata bag are promoted to typed columns: fast to filter, chart and join, not buried in JSON blobs.
RunAgain accepts the OTel GenAI keys plus common vendor aliases, so traces from most SDKs enrich correctly with zero configuration. Resource attributes apply to every span from a process; span attributes win when both are set.
Run the expensive LLM judge only where metadata.tier = premium; run strict structured-output checks only on the checkout agent. Enrichment isn't decoration; it routes your quality budget.
The sandbox proxy captures your agent's outbound HTTP calls, third-party APIs and internal services included, and lands them inside the same trace via trace-context propagation. The tool side of the loop stops being a blind spot.
The annotated stream: evals and context surface inline.
COMMON USE CASES
RELATED SOLUTIONS
Be first to run again.
Book 30 minutes and see the loop on your own agents, or write to tamas@runagain.ai.