Tracing records every step of the agent’s decisions!
This section uses a bank customer service robot to explain tracing, which is very intuitive.
When the user requests to reduce the overdraft fee, the agent will do intent classification, check the policy, check the account status, and then decide how to respond.
In the production system, every step needs to be recorded: what tools were used, what data was read, how much time it took, and which judgment affected the final answer.
Without trace, online problems can only be guessed.
With trace, you can see whether the agent's intent recognition is wrong, the tool call is wrong, the data has expired, or there is a problem with the policy document itself.
In regulated industries such as finance, medical care, and insurance, tracing also plays audit and compliance roles.
It is already a pre-launch capability.