Tracing
In systems and software engineering, the structured record left by an execution process, containing the inputs, outputs, intermediate states, and decision basis of each step. In LLM settings it supports auditing and fault localization.
Timeline (last 90 days)
In agent scenarios, observability usually consists of three parts: traces, metrics, and logs; a trace records the tree-structured call relationships of all steps within a single request, with each node containing input, output, state, and elapsed time.
For RAG agents, tracing needs to additionally capture retrieved document IDs, tool-call parameters and returns, and key metadata of model sampling.
The concept of observability emphasizes making the internal behavior of a system visible externally through means such as logs, metrics, and tracing.
All Facts (3)
In agent scenarios, observability usually consists of three parts: traces, metrics, and logs; a trace records the tree-structured call relationships of all steps within a single request, with each node containing input, output, state, and elapsed time.
50%UnverifiedFor RAG agents, tracing needs to additionally capture retrieved document IDs, tool-call parameters and returns, and key metadata of model sampling.
50%UnverifiedThe concept of observability emphasizes making the internal behavior of a system visible externally through means such as logs, metrics, and tracing.
50%